release
A release moves main, which users install the skill from, to dev. The skill pins npx -y cuetake@<version>, so the package must be on npm before main moves: a main that pins an unpublished version breaks every new install.
-
Start from a clean
dev.git statusis clean anddevmatchesorigin/dev.origin/mainis an ancestor oforigin/dev; if not, stop and show the user the commits only onmain. CI (Check) is green ondev's head. -
Account for every issue going out. List the commits in
origin/main..origin/devand the open issues labelledon-dev. GitHub closes an issue when a commit sayingCloses,FixesorResolves #Nreachesmain. Done when eachon-devissue either has such a commit, or the user has said it is done (close it by hand in step 8) or unfinished (swapon-devback to its triage label). Also list closing commits whose issue lackson-dev. -
Choose the version with the user. Before 1.0: a minor for features or breaking changes, a patch for fixes only. Name the breaking changes you found in step 2.
-
Prepare the release commit on
dev. Set the version inpackage.json,.claude-plugin/plugin.jsonandskills/cuetake/scripts/cuetake, and runbun installsobun.lockfollows. Done whengrep -rn '<old version>'outsidenode_modulesand.gitfinds nothing,bun test tests/pipeline.test.jspasses, andnpm pack --dry-runlistssrc,examples,README.mdandLICENSEand no install script. Commit asPrepare <version> with <the headline changes>and pushdev. -
Build the helper. The package ships
helper/bin/cuetake-capture, the Swift helper that records Apps (ADR 0009), which git ignores. On a Mac, from the release commit, the user runsbun run build:helper. Done whenlipo -archs helper/bin/cuetake-captureprints bothx86_64andarm64, andnpm pack --dry-runlistshelper/bin/cuetake-capture. If it is missing or has one architecture, stop: publishing would ship a CueTake that cannot record Apps. -
Publish to npm. This is the user's step, under their verified npm identity: hand them
npm publishto run from that commit, in the folder where the helper was built. Wait until they confirmcuetake@<version>is on npm. -
Move
mainand tag it.git checkout main && git merge --ff-only origin/dev, thengit tag -a v<version> -m "CueTake <version>", and pushmainand the tag. -
Write the GitHub release and tidy the issues. Create the release
CueTake <version>from the tag. Model its notes on the previous release's: one summary sentence, the install block with the new version, a bullet per user-visible change, then Breaking, Known issues, and the closing line naming the npm package built from this tag. Close the issues from step 2 that had no closing commit, with a comment naming the release. Removeon-devfrom every issue this release closed. Done when no open issue carrieson-dev.