Skip to content

refactor: replace info.json's repo with repoUrl - #88

Merged
dsherret merged 2 commits into
mainfrom
refactor_info_repo_url
Oct 3, 2026
Merged

dsherret merged 2 commits into
mainfrom
refactor_info_repo_url

Conversation

@dsherret

@dsherret dsherret commented Oct 3, 2026

Copy link
Copy Markdown
Member

#86 gave every info.json entry a repo (ex. g-plane/malva) to say where the plugin is published from. The served info.json already had a repoUrl for that, derived during the build, so each plugin ended up with both.

This drops repo and has info.json declare repoUrl instead, which the release lookup and the npm package map now read the GitHub owner and repo from:

{
  "name": "dprint_plugin_malva",
  "displayName": "g-plane/malva",
  "repoUrl": "https://github.com/g-plane/malva"
}

The served repoUrl values are unchanged; the only difference in the output is that repo is gone. Nothing reads it — the CLI doesn't and the homepage only had it in the search text, which repoUrl already covers.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
dprint-plugins 8587467 Commit Preview URL

Branch Preview URL
Oct 03 2026, 11:14 PM

@dsherret

dsherret commented Oct 3, 2026

Copy link
Copy Markdown
Member Author

This was up for only a few minutes so not a big deal.

@dsherret
dsherret added this pull request to the merge queue Oct 3, 2026
Merged via the queue into main with commit 0ac8cae Oct 3, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant