claude-code-plugin-release

# Version Bump & Release Workflow **IMPORTANT:** Plan and write detailed release notes before starting. **CRITICAL:** Commit EVERYTHING (including build artifacts). At the end of this workflow, NOTHING should be left uncommitted or unpushed. Run `git status` at the end to verify. ## Preparation 1. **Analyze**: Determine if the change is **PATCH** (bug fixes), **MINOR** (features), or **MAJOR** (breaking). 2. **Environment**: Identify repository owner/name from `git remote -v`. 3. **Paths — every file that carries the version string**: - `package.json` — **the npm/npx-published version** (`npx claude-mem@X.Y.Z` resolves from this) - `plugin/package.json` — bundled plugin runtime deps - `.claude-plugin/marketplace.json` — version inside `plugins[0].version` - `.claude-plugin/plugin.json` — top-level Claude-plugin manifest - `plugin/.claude-plugin/plugin.json` — bundled Claude-plugin manifest - `.codex-plugin/plugin.json` — Codex-plugin manifest - `openclaw/openclaw.plugin.json` — OpenClaw plugin manifest Verify coverage before editing: `git grep -l "\"version\": \"<OLD>\""` should list all seven. If a new manifest has been added since this doc was last updated, update this list. ## Workflow 1. **Update**: Increment the version string in every path above. Do NOT touch `CHANGELOG.md` — it's regenerated. 2. **Verify**: `git grep -n "\"version\": \"<NEW>\""` — confirm all seven files match. `git grep -n "\"version\": \"<OLD>\""` — should ...