chore(registry): rebuild plugin index so /plugins shows Extra Charts - #205
Merged
Conversation
The merge of #204 added fyi.xnet.charts-extra to registry/first-party.json, but the Plugins Registry `rebuild` job that regenerates registry/registry.json failed: it cannot push to main (branch protection — github-actions[bot] is not a ruleset bypass actor). So the committed index — which the website's /plugins page and the in-app marketplace both read — still listed only 3 plugins. Regenerate registry.json from the sources (4 built-in, 0 community) so the marketplace shows the Extra Charts plugin. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
✓ Changelog fragment found — thanks! |
Contributor
|
Preview removed for PR #205. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The public /plugins page (and the in-app marketplace) still showed only 3 plugins after #204, even though that PR added
fyi.xnet.charts-extratoregistry/first-party.json.Root cause: the site reads the committed flat index
registry/registry.json(viasite/src/data/plugins.ts), which is regenerated fromfirst-party.json+community.jsonbyscripts/build-plugin-index.mjs. ThePlugins Registryworkflow'srebuildjob fired on the merge to main and produced the correct index — but itsgit pushwas rejected by branch protection (GH013: Changes must be made through a pull request;github-actions[bot]is not a ruleset bypass actor). Soregistry.jsonwas never updated.This PR lands the regenerated index through a normal PR.
Change
registry/registry.json— regenerated: 4 built-in + 0 community (adds the Extra Charts entry).node scripts/build-plugin-index.mjs --checkpasses.revoked.jsonunchanged.After deploy, https://xnet.fyi/plugins/ will list 4 plugins (a new "visualization" category filter appears).
Note on the systemic gap
This will recur for every future
first-party.jsonchange: the auto-rebuild bot can't push tomain. Fixing it properly means making the rebuild job's committer a ruleset bypass actor (the same fix applied to the changelog PR-stamping App in exploration 0203), or having the job open a PR instead of pushing. Out of scope here — flagged for follow-up.🤖 Generated with Claude Code