bump-version

Bump Version

Overview

sci-brain is a Claude Code plugin. Its version is declared in three JSON files that must stay in lockstep — the marketplace reads it from marketplace.json, plugin tooling reads it from plugin.json, and npm/pi read it from package.json. CI (scripts/validate_skills.py) fails if they diverge, and .github/workflows/publish.yml refuses to publish unless the pushed tag equals v + package.json's version. A release is: bump all three files → commit → annotated tag → push → GitHub release.

Version Source of Truth

File	Path to version
.claude-plugin/plugin.json	.version
.claude-plugin/marketplace.json	.plugins[0].version
package.json	.version

All three MUST match. If they diverge, CI's version-sync check fails, the npm publish tag gate rejects the release, and the marketplace and the installed plugin report different versions.

When to Use

• "tag a version", "bump version", "cut a release", "release v0.x"
• After a batch of merged PRs that warrants a new release
• Before announcing changes that downstream users need to pull

Do NOT use for:

• Pre-release / draft tags (the workflow below assumes a real release)
• Hotfix to an old branch — this skill assumes you tag from main

Bump Type → New Version

Read current version from .claude-plugin/plugin.json, then:

• patch (X.Y.Z → X.Y.Z+1): bugfix, doc tweak, no behavior change
• minor (X.Y.Z → X.Y+1.0): new skill, new feature, additive change
• major (X.Y.Z → X+1.0.0): breaking change to a skill's contract / removed skill

If the user didn't specify, ask which bump type (patch/minor/major) before continuing.

Procedure

1. Read current version from .claude-plugin/plugin.json and confirm marketplace.json and package.json match. If they already disagree, stop and flag it — don't paper over the drift.

2. Edit all three files to the new version. Use the Edit tool, not sed, so the diff is reviewable.