Version Bump & Release Workflow

IMPORTANT: You must first plan and write detailed release notes before starting the version bump workflow.

CRITICAL: ALWAYS 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

• Analyze: Determine if the change is a PATCH (bug fixes), MINOR (features), or MAJOR (breaking) update.

• Environment: Identify the repository owner and name (e.g., from git remote -v ).

• Paths: Verify existence of package.json , .claude-plugin/marketplace.json , and plugin/.claude-plugin/plugin.json .

Workflow

• Update: Increment version strings in all configuration files.

• Verify: Use grep to ensure all files match the new version.

• Build: Run npm run build to generate fresh artifacts.

• Commit: Stage all changes including artifacts: git add -A && git commit -m "chore: bump version to X.Y.Z" .

• Tag: Create an annotated tag: git tag -a vX.Y.Z -m "Version X.Y.Z" .

• Push: git push origin main && git push origin vX.Y.Z .

• Release: gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES" .

• Changelog: Regenerate CHANGELOG.md using the GitHub API and the provided script: gh api repos/{owner}/{repo}/releases --paginate | ./scripts/generate_changelog.js > CHANGELOG.md

• Sync: Commit and push the updated CHANGELOG.md .

• Notify: Run npm run discord:notify vX.Y.Z if applicable.

• Finalize: Run git status to ensure a clean working tree.

Checklist

• All config files have matching versions

• npm run build succeeded

• Git tag created and pushed

• GitHub release created with notes

• CHANGELOG.md updated and pushed

• git status shows clean tree