Plugin version bump
Skill halyard-labs/claude-plugin-marketplace/.claude/skills/plugin-version-bump
Bump plugin version on every commit. ALWAYS use this skill when committing changes to this repository. The Claude Code plugin cache keys on the version field in plugin.json — if the version isn't bumped, users get stale cached plugins missing new features, hooks, and fixes. Trigger on: /commit, "commit", "git commit", or any action that creates a git commit.From its SKILL.md
npx -y skills add halyard-labs/claude-plugin-marketplace --skill plugin-version-bumpAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, as published. Nobody here has run it
Plugin Version Bump
Before every commit in this repo, bump the version field in each changed plugin's plugin.json.
Why
Claude Code caches plugins by version string. If you push changes but keep the same version, users' caches serve the old plugin until they manually clear it. Bumping the version ensures fresh installs always get the latest.
Process
- Identify which
plugins/*/directories have staged changes (usegit diff --cached --name-only) - For each affected plugin, read
.claude-plugin/plugin.json,.codex-plugin/plugin.json, and.cursor-plugin/plugin.json - Bump the patch version (e.g.
1.0.0→1.0.1,1.2.3→1.2.4) in all three plugin manifests - Update the matching plugin entry's
versionfield in the root.claude-plugin/marketplace.jsonto the same new version. - Bump the catalog-level
metadata.versionin BOTH.claude-plugin/marketplace.jsonand.cursor-plugin/marketplace.json(patch by default; minor/major if the per-plugin bump is minor/major). Always bump it on every update — never skip. - Skip
.agents/plugins/marketplace.json(Codex marketplace) and the Cursor marketplace plugin entries — they intentionally have no per-plugin version field today. Only update one if aversionfield is already present in the plugin entry. - Stage all updated files (all three plugin.json files,
.claude-plugin/marketplace.json, and.cursor-plugin/marketplace.json) - Proceed with the commit
Rules
- Always bump patch unless the commit message explicitly says
BREAKING:(bump major) or adds new user-facing features like skills/hooks (bump minor) - If multiple plugins changed, bump each independently
- Never skip the bump — even for docs-only changes, since docs are bundled in the plugin