fix(release): bump codex/claude plugin.json manifests to 0.1.7#56
Merged
Conversation
The publish.yml version-consistency gate failed the v0.1.7 tag: the codex .codex-plugin/plugin.json and claude .claude-plugin/plugin.json manifests were still pinned at 0.1.6 (the release-prep commit bumped the .mcp.json npx pins but missed these sibling manifests). The cross-adversarial review caught the .mcp.json pins but not the plugin.json manifests. All versions now 0.1.7; re-tagging.
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.
What & why
The
v0.1.7tag'spublish.ymlrun failed its version-consistency gate: the codex.codex-plugin/plugin.jsonand claude.claude-plugin/plugin.jsonmanifests were still pinned at0.1.6. The release-prep commit bumped the.mcp.jsonnpx pins (caught by the cross-adversarial review) but missed these sibling manifests.The tag was re-pointed at this fix and 0.1.7 is already published to npm + GitHub Release (all 7 packages). This PR lands the fix on
mainso the default branch matches the published tag.Checklist
No code change beyond the two manifest version fields.