| name | cut-stable-release |
| description | Cut a coco stable release from `master` or finalize a selected RC cutoff from an existing `release/X.Y.Z-rc` branch while `master` continues independently. Use when the user asks to create a stable `vX.Y.Z` release, preserve an RC's runtime source, finalize Changesets prerelease metadata, validate and build the release, commit and tag it, and push the source branch plus tag. Supports dry-run, preview, and rehearsal requests by stopping before push. |
Cut Stable Release
Purpose
Run the local git-side workflow for a stable coco release. This skill prepares
the stable release commit and tag only; npm publish happens later when a GitHub
Release is created for the tag.
Use this for tags like v2.0.0. Use $cut-rc-release for RC tags like
v2.0.0-rc.0.
Safety
- Work from a clean dedicated release worktree. If
git status -sb shows local
changes, stop.
- Do not run
changeset publish and do not create a GitHub Release from this
skill.
- Stable release tags must not contain
.changeset/pre.json; the repo
validator enforces this.
- For stable-from-RC releases, preserve the selected RC as the source cutoff.
The stable commit may change only Changesets metadata, package manifests,
and package changelogs.
- Keep
master work that landed after the RC out of the stable tag. Back-merge
the stable release metadata into master after the release cut.
- Treat
dry run, dry-run, --dry-run, preview, or rehearsal as a
request to create the local commit and tag but skip pushing.
- Networked git commands usually need escalation.
Choose The Path
- Direct stable release: start from with pending changesets and no RC
cycle.
