All packages/* publish at one shared version via pnpm native versioning (versioning.fixed in pnpm-workspace.yaml). Private examples, demo and fixtures are excluded with versioning.ignore.
Releases are packed and published with pnpm, never npm. Internal ranges are workspace:^, and only pnpm rewrites them to real semver ranges in the tarball. npm publish would ship the workspace: protocol and break installs.
pnpm change statusshows the pending intents and the planned versions.pnpm version -rbumps the fixed group, consumes the intents and writes aCHANGELOG.mdinside every package.node scripts/changelog-root.mjswrites the new version's entry into the rootCHANGELOG.md, grouped as Breaking, Features and Fixes, and wraps it in<!-- release:start -->and<!-- release:end -->. Edit the entry for voice. Re-running keeps your edits.- Verify:
pnpm change check,pnpm -r build,pnpm -r test,pnpm smoke:pack,pnpm docs:build. - Commit as the release PR (
chore(release): v<version>) and merge it. - Tag
v<version>on main and push the tag.
The tag push triggers .github/workflows/release.yml. It verifies every package.json matches the tag, then publishes every package in versioning.fixed (all nine) one by one with pnpm --filter <pkg> publish, in dependency order, behind the npm-publish environment approval.
The publish loop in .github/workflows/release.yml is hand-maintained. node scripts/check-published-list.mjs fails CI when it drifts from versioning.fixed, so a package added to the group cannot be silently left unpublished. Run it after editing either list.
npm cannot roll back. If a publish fails part way, fix the cause and re-run the failed job. Do not re-tag once anything has been published.
Things learned in the v0.2.0 release:
- A tag runs the workflow file as it was at the tagged commit. A workflow fix after a failed run therefore needs the tag moved onto the fixed commit. That is only safe when nothing was published and no GitHub release exists (check
npm view @chttp/<name>@<version>for every package andgh release list). - Each job installs from scratch. A step that
verifyneeds (like the scriptc exec-bitchmod) is not inherited bypublish, sopublishbuilds only./packages/*. - A brand new package name can read as 404 from the registry for about five minutes after a successful publish. Trust the
Published packageline in the log, wait, then check again. Do not re-runpublishinside that window: the already-published skip relies onnpm view, which can lag the same way. pnpm versioning.ignoretakes exact package names, not globs.- Tags are not always ancestors of main (v0.1.0 is not), so
release-notes.shpicks the previous tag by version order instead ofgit describe.