fix(release): sync plugin + README versions during release cut - #21
Merged
Conversation
`npm version` in the release script bumped package.json only, but src/version-consistency.test.ts requires plugin/package.json, plugin/manifest.json, and the README `Latest: **vX.Y.Z**` badge to equal the CLI version. The mismatch failed publish.yml's Test step AFTER the v2.3.1 tag was already pushed, forcing a manual sync + tag move. Add Phase 3b: after the version bump, mirror the new version into the two plugin JSON files and the README badge (fail-fast if the badge marker is missing), and stage all three in the release commit so the tagged commit is internally consistent and CI stays green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Problem
scripts/release.mjsrunsnpm versionwhich bumpspackage.jsononly.But
src/version-consistency.test.ts(Issue #14 / P4) requiresplugin/package.json,plugin/manifest.json, and the READMELatest: **vX.Y.Z**badge to all equal the CLI version.On the v2.3.1 cut this drift failed
publish.yml's Test step after thetag was already pushed — no npm publish or GitHub Release happened, and it
required a manual sync + tag-move to recover. Left unfixed, every future
npm run releasehits the same wall.Fix
Add Phase 3b to the release script: right after the version bump, mirror
the version into the two plugin JSON files and the README badge
(fail-fast if the badge marker is absent), and stage all three in the
release commit so the tagged commit is internally consistent.
Verification
plugin package, manifest, and README all synced; the three consistency
assertions pass (the CHANGELOG assertion is handled by the existing Phase 4).
node --checkOK · prettier clean · regex matches the real README line andrejects a missing marker.
No production code changes — release tooling only.
🤖 Generated with Claude Code