Skip to content

Human action 240

Jerry Holland edited this page Nov 14, 2026 · 5 revisions

Complete the v0.22.1 release

Procedure for issue #240. The issue is the record of ownership, status and completion evidence; this page is the execution instruction.

Done 2026-10-14. v0.22.1 is released on GitHub and npm; the evidence is on the issue. The page stays as the reference for publishing by hand (step 3) while npm/cli#9969 refuses the tag run's trusted publish. Since 2026-11-13 the current hand publish is Human-action-139, "Until step 6", with scripts/publish-npm.ps1.

Owner role: the repository owner (jwh3times), who can push a v* tag and publish a GitHub release, and who owns the npm holland-vip organization.

What this completes: the 0.22 line, which ends the vcs-lab migration window (ADR-0039 §8), carries the notice that v0.23.0 removes the vlab alias, and finishes the rename in what the product prints. The release candidate is 7e5f89961df44684173e1dfda4f260b426ba494e on main.

Why v0.22.1 and not v0.22.0: the v0.22.0 tag (on b81cd0f) ran, but its publish step failed under npm 12 before anything reached npm (#240). The owner chose on 2026-10-13 to fix the workflow and release v0.22.1. The v0.22.0 tag stays, immutable; its draft release was deleted. 0.22.1 ships everything 0.22.0 lists.

When: as soon as the three gate runs are green. Until it is done, package.json and the README describe a release that does not exist.

Prerequisites

  • gh signed in with push access to jwh3times/causet, in any clean checkout.
  • For the last step, a machine with Git, and Node.js for the npm half. Linux or Windows; nothing is built on it.
  • An npm session for an owner of the holland-vip organization, with two-factor authentication, for step 3 (see there for why). Node.js 22.14 or later and npm 11.5.1 or later.

Step 1: confirm the three gate runs

All three were dispatched against 7e5f899 on 2026-10-14. Their results are recorded on #240. Confirm before tagging:

  1. Run 38509822626 (ci, manual dispatch). Expected: every job green: six modes on Ubuntu and on Windows, the Node 20 jobs, and static checks. Release gates 1, 2, 3, 6, 7 and 8.
  2. Run 38509824626 (release-gates). Expected: both runners green. Gates 4, 5 and 10.
  3. Run 38509827028 (release, manual dispatch). Expected: both build jobs, assemble the package set and both install and smoke-test jobs green; the attest-and-publish job skipped. Gate 9.
  4. If any failed, stop. Record the failing job on #240 and do not tag.

A routine PR or main run does not stand in for these. If main has moved since, tag the candidate, not the tip.

Step 2: tag the release

The owner directed on 2026-10-14 that the agent pushes this tag once all three gates are green; its run is recorded on #240. The commands are kept here for a re-run by hand.

git fetch origin
git tag -a v0.22.1 7e5f89961df44684173e1dfda4f260b426ba494e -m "causet 0.22.1"
git push origin v0.22.1

The tag starts the release workflow. Watch it:

gh run list --repo jwh3times/causet --workflow release.yml --limit 1
gh run watch --repo jwh3times/causet <run id>

Expected: every job green, including attest and draft the release, and publish to npm when enabled. Unlike v0.21.0, its Publish to npm with provenance step runs, because NPM_PUBLISH is true. A draft release named causet v0.22.1 exists with these assets:

  • holland-vip-causet-0.22.1.tgz
  • holland-vip-causet-win32-x64-0.22.1.tgz
  • holland-vip-causet-linux-x64-gnu-0.22.1.tgz
  • cst-0.22.1-x86_64-pc-windows-msvc.zip
  • cst-0.22.1-x86_64-unknown-linux-gnu.tar.gz
  • install.sh and install.ps1
  • SHA256SUMS

If the tag is on the wrong commit: release tags are immutable under the repository's rulesets. This is recoverable only before anything is published to npm, which now happens in the same run, so check the commit before pushing. If it is wrong and the publish step has not run, cancel the run, disable the ruleset "release tags are immutable", delete and re-create the tag, delete the draft release, enable the ruleset again, and say so on #240. If a package was already published, stop and record it: that version exists for good, and the fix is a new patch release.

Step 3: publish the three packages by hand

Status 2026-10-14: the tag run (38513269265) drafted the release with every asset, but npm refused the workflow's publish with E403 OIDC permission denied for this action. This repository's OIDC tokens use GitHub's immutable subject claims since its rename, and npm's trusted publishing does not match them yet (npm/cli#9969). Nothing was published. The settings configured for #139 are not at fault; leave them as they are.

So this release is published by hand, as v0.21.0 was. Publishing access disallows tokens, which still permits an interactive publish with two-factor authentication.

  1. Download the assets into an empty directory and check them:

    mkdir release-0.22.1 && cd release-0.22.1
    gh release download v0.22.1 --repo jwh3times/causet
    sha256sum --check --ignore-missing SHA256SUMS

    Expected: OK for all seven files. On Windows without sha256sum, compare Get-FileHash -Algorithm SHA256 <file> with the line in SHA256SUMS.

  2. Sign in, then publish the platform packages first, so the main package never names one that is absent. npm prompts for a one-time password on each:

    npm login
    npm whoami
    npm publish ./holland-vip-causet-win32-x64-0.22.1.tgz --access public
    npm publish ./holland-vip-causet-linux-x64-gnu-0.22.1.tgz --access public
    npm publish ./holland-vip-causet-0.22.1.tgz --access public

    Keep the ./: npm 12 reads a bare holland-vip-….tgz path with a slash in it as a GitHub repository.

  3. Check all three. The registry can take several minutes to show a new version:

    npm view @holland-vip/causet-win32-x64@0.22.1 dist.shasum
    npm view @holland-vip/causet-linux-x64-gnu@0.22.1 dist.shasum
    npm view @holland-vip/causet@0.22.1 dist.shasum optionalDependencies bin

    Expected: the shasums 80b739952d92cbc23c12c7d5aede5c6a7397df42, c0ccbc957c6aa896becfe97a67eea39e4afc1bb7 and b2b8bc0a9b7e3f95715731f0367a0d11fa5bc63a; the main package lists both platform packages at exactly 0.22.1, and bin names cst and vlab.

If a publish fails: stop and record the exact npm error on #240. A version, once published, cannot be published again; do not retry with a changed tarball. If only the main package failed, the platform packages are harmless by themselves. Never add an npm token to the repository to get past a failure.

There is no need to re-run the tag's workflow afterwards: its other steps all passed, and a re-run would only fail again at the publish.

Step 4: publish the GitHub release

The install scripts download from a published release; a draft's assets are not served at releases/latest/download.

gh release edit v0.22.1 --repo jwh3times/causet --draft=false --latest \
  --notes "Ends the vcs-lab migration window, and gives notice that v0.23.0 removes the vlab alias. v0.22.0 was tagged but never published; this release ships everything it lists. See CHANGELOG.md, sections 0.22.1 and 0.22.0."

Expected: gh release view v0.22.1 --repo jwh3times/causet shows it as the latest release.

Step 5: verify an install each way

On one machine, in an empty scratch directory. Linux is shown; on Windows use install.ps1 -Prefix and cst.exe, as in the v0.21.0 procedure step 6.

curl -fsSLO https://github.com/jwh3times/causet/releases/latest/download/install.sh
sh install.sh --prefix ./script-prefix
./script-prefix/cst --version

npm install -g --prefix ./npm-prefix --allow-scripts=@holland-vip/causet @holland-vip/causet@0.22.1
./npm-prefix/bin/cst --version

Expected: causet 0.22.1 from both.

  • A refusal that names a SHA-256 mismatch means the release's assets and SHA256SUMS disagree. Stop and record it.
  • This release refuses an unmigrated repository. If you try the new cst in a repository that still has refs/notes/vcs-lab and no refs/notes/causet, the refusal unmigrated-repository is the release working. Run cst migrate there.

Remove the scratch directory afterwards.

Completion evidence

Attach to #240:

  • the three run links from step 1 and the tag's run from step 2, with their conclusions;
  • the three dist.shasum values from step 3;
  • the release URL;
  • the two --version outputs from step 5.

Then remove human-action-required from #240, set its board card to Done, and point the Human TODO entry at the completed outcome. Record the tag's run on #139 as the proof of trusted publishing; #139 can then be closed. #231 becomes eligible for v0.23.0.

Clone this wiki locally