fix(release): bump plugin manifests in set-version#1051
Merged
miguel-heygen merged 3 commits intoMay 23, 2026
Merged
Conversation
scripts/set-version.ts only bumped the npm package.json files, so the Claude Code / Codex / Cursor plugin manifests stayed at 0.1.0 across every release. Claude Code gates /plugin update on plugin.json's version, so users never received accumulated changes (closes heygen-com#1048). Add a PLUGINS list and a parallel loop that rewrites each manifest's version, and include the manifests in the clean-tree guard and the staged file set. The loop replaces only the version string (not a JSON round-trip) to preserve each file's exact formatting, since oxfmt keeps their short arrays inline and JSON.stringify would expand them and fail the pre-commit format check.
Catch the three plugin manifests up to the current release version so /plugin update is unfrozen immediately, rather than waiting for the next release to sync them via the fixed-versioning script.
miguel-heygen
requested changes
May 23, 2026
Collaborator
miguel-heygen
left a comment
miguel-heygen
left a comment
There was a problem hiding this comment.
Manifests should catch up to 0.6.40 (just released), not 0.6.39. One-line fix per manifest.
Contributor
Author
Ok, doing that |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| stdio: "inherit", | ||
| }, | ||
| ); | ||
| execSync(`git commit -m "chore: release v${version}"`, { |
Contributor
Author
|
Done — bumped all three plugin manifests ( |
miguel-heygen
approved these changes
May 23, 2026
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
3 participants
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
scripts/set-version.tsonly bumped the npmpackage.jsonfiles, so the Claude Code / Codex / Cursor plugin manifests (.claude-plugin/,.codex-plugin/,.cursor-plugin/plugin.json) stayed frozen at0.1.0across every release. Claude Code gates/plugin updateonplugin.json'sversion, so users never received accumulated changes.Closes #1048.
Changes
scripts/set-version.ts: add aPLUGINSlist and a parallel loop (mirroring the existingpackage.jsonloop) that rewrites each manifest'sversion, plus include the manifests in the clean-tree guard and the staged file set.JSON.parse/JSON.stringify, to preserve each file's exact formatting:oxfmtkeeps these manifests' short arrays (e.g."capabilities": ["Read", "Write"]) inline, whileJSON.stringifyexpands them — which would fail the pre-commitoxfmt --checkon the release commit this script itself creates..claude-plugin/.codex-plugin/.cursor-pluginup to the current release version0.6.39, so/plugin updateunfreezes on merge rather than waiting for the next release.Verification
bun run set-version 0.6.39 --no-tagfrom a clean baseline produces a version-only diff (one line per manifest),0.1.0 → 0.6.39.oxfmt --checkpasses on all three manifests (also confirmed by the pre-commit hook on the catch-up commit).