Repository navigation
Human action 267
Procedure for issue #267. The issue is the record of ownership, status and completion evidence; this page is the execution instruction.
Owner role: an owner of the npm holland-vip organization, for step 1 only. The agent does
steps 2 and 3 once step 1 is recorded.
What this completes: v0.25.0, which makes cst the one command (ADR-0040): cst fetch,
pull, push and clone carry the causal records, and every other command runs Git. The release
commit is 53b671b on main (the full hash is on #267), tagged v0.25.0.
Done 2026-10-16. v0.25.0 is released on GitHub and npm; the evidence is on the issue. The page
stays as the reference for publishing by hand (step 1) 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.
- A machine with Git, Node.js 22.14 or later and npm 11.5.1 or later, and
ghsigned in. Linux or Windows; nothing is built on it. - An npm session for an owner of
holland-vip, with two-factor authentication. Publishing access disallows tokens, which still permits an interactive publish with 2FA.
-
Download the assets into an empty directory and check them:
mkdir release-0.25.0 && cd release-0.25.0 gh release download v0.25.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.25.0.tgz --access public npm publish ./holland-vip-causet-linux-x64-gnu-0.25.0.tgz --access public npm publish ./holland-vip-causet-0.25.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; add
--prefer-onlineifnpm viewsays the version is missing:npm view @holland-vip/causet-win32-x64@0.25.0 dist.shasum --prefer-online npm view @holland-vip/causet-linux-x64-gnu@0.25.0 dist.shasum --prefer-online npm view @holland-vip/causet@0.25.0 dist.shasum optionalDependencies bin --prefer-online
Expected: the shasums
425e4886b946ee8f8d63a23a46364fae9cf8b8e1(win32-x64),393e35ec6dce95c767249adf7cd8ba603331a874(linux-x64-gnu) and88a0238a9bc7dba6b6406749ad0a174a7853ece2(main), as recorded on #267; the main package lists both platform packages at exactly0.25.0, andbinnamescstonly. -
Say on #267, or to the agent, that it is done.
If a publish fails: stop and record the exact npm error on #267. 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: it 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.25.0 --repo jwh3times/causet --draft=false --latest \
--notes "cst is the one command: cst fetch, pull, push and clone carry the causal records, and every other command runs Git (ADR-0040). See CHANGELOG.md, section 0.25.0."Expected: gh release view v0.25.0 --repo jwh3times/causet shows it as the latest release.
In an empty scratch directory on Linux; 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 --prefer-online --prefix ./npm-prefix --allow-scripts=@holland-vip/causet @holland-vip/causet@0.25.0
./npm-prefix/bin/cst --versionExpected: causet 0.25.0 from both. A refusal that names a SHA-256 mismatch means the
release's assets and SHA256SUMS disagree; stop and record it.
Attach to #267: the three dist.shasum values
from step 1, the release URL, and the two --version outputs from step 3. Then remove
human-action-required from #267, set its board card to Done, and point the
Human TODO entry at the completed outcome.