fix: reconcile plugin.json manifest with repo and CI-gate it#39
Merged
Conversation
- plugin.json: bump version to 0.5.0 and enumerate snippets (17), templates (2), and examples (4) alongside skills and rules - validate.yml: new validate-manifest job asserting every manifest path exists, every content file/dir on disk is listed, and manifest version equals VERSION - release.yml: new step rewrites the plugin.json version line on each release so the pipeline owns it - AGENTS.md: document the new job and ownership Closes #28 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
github-actions
Bot
added
documentation
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
1 participant
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
Fixes #28. The
.cursor-plugin/plugin.jsonmanifest had drifted: pinned at 0.2.3 while the repo is at 0.5.0, and listing only skills and rules.snippets(17 files),templates(2 dirs), andexamples(4 dirs) arrays mirroring the existing relative-path style.validate-manifestjob — every manifest path must exist on disk, every skill/rule/snippet/template/example on disk must be in the manifest, and manifestversionmust equalVERSION.Sync plugin manifest versionstep rewrites the manifestversionline on each release (the externalrelease-doc-sync@v1action can't be extended from here, so the pipeline owns the line directly).Testing
Ran the validator locally: passes clean, and a deliberately broken manifest (dropped snippet + wrong version) produces exactly 2 errors and exit 1. The release-step regex verified to rewrite only the top-level version line.
🤖 Generated with Claude Code