Repository navigation
Human action 245
Procedure for issue #245. The issue is the record of ownership, status and completion evidence; this page is the execution instruction.
Done 2026-10-14. v0.23.0 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: v0.23.0, which removes the vlab command alias (#231, ADR-0038 §4), as
v0.22.1 announced, and ends ADR-0037's oracle period. The release candidate is
6aae8da1de100dd915d34deb7fad372ff55c0509 on main.
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.
-
ghsigned in with push access tojwh3times/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-viporganization, with two-factor authentication, for step 3. Node.js 22.14 or later and npm 11.5.1 or later.
All three were dispatched against 6aae8da on 2026-10-14. Their results are recorded on
#245. Confirm before tagging:
-
Run 38634416913 (
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. -
Run 38634420209
(
release-gates). Expected: both runners green. Gates 4, 5 and 10. -
Run 38634423445 (
release, manual dispatch). Expected: bothbuildjobs,assemble the package setand bothinstall and smoke-testjobs green; the attest-and-publish job skipped. Gate 9. - If any failed, stop. Record the failing job on #245 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.
The owner directed on 2026-10-14 that the agent carries this release through, so the agent pushes the tag once all three gates are green and records its run on #245. The commands are kept here for a re-run by hand.
git fetch origin
git tag -a v0.23.0 6aae8da1de100dd915d34deb7fad372ff55c0509 -m "causet 0.23.0"
git push origin v0.23.0The 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: the build, assembly and smoke jobs green, and a draft release named
causet v0.23.0 with these assets:
holland-vip-causet-0.23.0.tgzholland-vip-causet-win32-x64-0.23.0.tgzholland-vip-causet-linux-x64-gnu-0.23.0.tgzcst-0.23.0-x86_64-pc-windows-msvc.zipcst-0.23.0-x86_64-unknown-linux-gnu.tar.gz-
install.shandinstall.ps1 SHA256SUMS
NPM_PUBLISH is true (owner, 2026-10-14), so the publish step runs. While
npm/cli#9969 stands, expect it to fail with E403 OIDC permission denied for this action after the release is drafted, with nothing published; go on to
step 3. This repository's OIDC tokens use GitHub's immutable subject claims since its rename, and
npm's trusted publishing does not match them yet. The settings configured for #139 are not at
fault. If the publish succeeds, npm has fixed the bug: skip step 3, and record the run on
#139 as its proof.
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. If it is wrong and nothing is published, 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 #245. If a package was already published, stop and record it: that version exists for good, and the fix is a new patch release.
Status 2026-10-14: the tag run (38640094723)
drafted the release with every asset and was refused at the npm publish (E403, npm/cli#9969), as
expected. Nothing was published. Required now: this step.
Publishing access disallows tokens, which still permits an interactive publish with two-factor authentication.
-
Download the assets into an empty directory and check them:
mkdir release-0.23.0 && cd release-0.23.0 gh release download v0.23.0 --repo jwh3times/causet sha256sum --check --ignore-missing SHA256SUMS
Expected:
OKfor all seven files. On Windows withoutsha256sum, compareGet-FileHash -Algorithm SHA256 <file>with the line inSHA256SUMS. -
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.23.0.tgz --access public npm publish ./holland-vip-causet-linux-x64-gnu-0.23.0.tgz --access public npm publish ./holland-vip-causet-0.23.0.tgz --access public
Keep the
./: npm 12 reads a bareholland-vip-….tgzpath with a slash in it as a GitHub repository. Each publish answersYour package is being processed; that is success. -
Check all three. The registry can take several minutes to show a new version, and
npm viewcan answer from a stale local cache; add--prefer-onlineif it says the version is missing:npm view @holland-vip/causet-win32-x64@0.23.0 dist.shasum --prefer-online npm view @holland-vip/causet-linux-x64-gnu@0.23.0 dist.shasum --prefer-online npm view @holland-vip/causet@0.23.0 dist.shasum optionalDependencies bin --prefer-online
Expected: the shasums
06aef83323f50926a00f6ab96ff75b070328363b(win32-x64),c434908ad637a46b072226b53d8e8c1b848efcd7(linux-x64-gnu) and7276c9b725db608903ef522d725b0e90f29d9ead(main), as recorded on #245; the main package lists both platform packages at exactly0.23.0, andbinnamescstonly.
If a publish fails: stop and record the exact npm error on #245. 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.
The install scripts download from a published release; a draft's assets are not served at
releases/latest/download.
gh release edit v0.23.0 --repo jwh3times/causet --draft=false --latest \
--notes "Removes the vlab command alias: cst is the only command. See CHANGELOG.md, section 0.23.0."Expected: gh release view v0.23.0 --repo jwh3times/causet shows it as the latest release.
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
ls ./script-prefix
npm install -g --prefer-online --prefix ./npm-prefix --allow-scripts=@holland-vip/causet @holland-vip/causet@0.23.0
./npm-prefix/bin/cst --version
ls ./npm-prefix/binExpected: causet 0.23.0 from both, and each listing holds cst and no vlab.
- A refusal that names a SHA-256 mismatch means the release's assets and
SHA256SUMSdisagree. Stop and record it.
Remove the scratch directory afterwards.
Attach to #245:
- the three run links from step 1 and the tag's run from step 2, with their conclusions;
- the three
dist.shasumvalues from step 3; - the release URL;
- the two
--versionoutputs from step 5.
Then remove human-action-required from #245, set its board card to Done, and point the
Human TODO entry at the completed outcome.