nahumlitvin / release
Cut a prismantis release - version bump, changelog, verify, tag and push. Use when asked to "release", "bump the version", "ship 0.x" or "publish".
0
SKILL.md2.0 KB
Release
- Pick the version. Breaking option or token renames are minor while below 1.0 (and major after). New features are minor. Fixes are patch.
- Set it in both manifests:
versionin.claude-plugin/plugin.jsonandplugins[0].versionin.claude-plugin/marketplace.json. - Changelog: rename
## [Unreleased]at the top of docs/CHANGELOG.md to a dated## [x.y.z], keeping Added, Changed and Fixed, written for users. Merged PRs already put their entries there. - Vendor: if
scripts/package.jsonchanged, runnpm --prefix scripts run build:vendor, and confirm the bundle has noimportstatements and no non-MIT code (grep -c -i elk hooks/vendor/*.jsmust print 0). - Verify: run every step in AGENTS.md Verify, plus
live-check. Fresh install test against a throwaway config:
`
CLAUDECONFIGDIR=<scratch>/fresh claude plugin marketplace add NahumLitvin/prismantis
CLAUDECONFIGDIR=<scratch>/fresh claude plugin install prismantis@prismantis
CLAUDECONFIGDIR=<scratch>/fresh claude plugin list`
Run it after pushing; the marketplace clones from GitHub.- Release PR:
mainonly takes merges through a PR with green checks, so open the release commit as a PR and merge it. - Tag main:
git tag vX.Y.Z <merge commit> && git push origin vX.Y.Z. Thereleaseworkflow checks the tag againstplugin.json, checks the tag is onmain, and publishes the GitHub release from the CHANGELOG section. - Pin the release: a second PR sets
reftovX.Y.Zandshato the tagged commit in thesourceof.claude-plugin/marketplace.json. Until it merges, installs keep getting the previous release. - Confirm CI and the release workflow are green, then run the fresh install test and check
claude plugin listshows the new version.