Skip to content

Human action 274

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

Complete the v0.25.1 release

Procedure for issue #274. 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.1, two fixes to 0.25.0: a value option spelled in camel case (--generatedBy agent) is refused instead of recording provenance for an actor true (#262), and cst --help describes --engine native as it behaves (#271). The release commit is 658c200 on main (the full hash is on #274), tagged v0.25.1.

Done 2026-10-17. v0.25.1 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.

Prerequisites

  • A machine with Git, Node.js 22.14 or later and npm 11.5.1 or later, and gh signed 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.

Step 1: publish the three packages by hand

  1. Download the assets into an empty directory outside any checkout (one inside the causet checkout leaves it dirty, which blocks cst merge and fails the repository hygiene tests), and check them:

    mkdir -p ~/Downloads/release-0.25.1 && cd ~/Downloads/release-0.25.1
    gh release download v0.25.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.25.1.tgz --access public
    npm publish ./holland-vip-causet-linux-x64-gnu-0.25.1.tgz --access public
    npm publish ./holland-vip-causet-0.25.1.tgz --access public

    Keep the ./: npm 12 reads a bare holland-vip-….tgz path with a slash in it as a GitHub repository. Each publish answers Your package is being processed; that is success.

  3. Check all three. The registry can take several minutes to show a new version; add --prefer-online if npm view says the version is missing:

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

    Expected: the shasums 32a2c00588b4025d9b8259baad8f8bdae837981a (win32-x64), 19d70b6acd60e371673e011e3715334e3cbdc73c (linux-x64-gnu) and ff04a73efae6f6692d75368a95e8dd91496e0c49 (main), as recorded on #274; the main package lists both platform packages at exactly 0.25.1, and bin names cst only.

  4. Say on #274, or to the agent, that it is done.

If a publish fails: stop and record the exact npm error on #274. 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.

Step 2: publish the GitHub release (agent)

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

gh release edit v0.25.1 --repo jwh3times/causet --draft=false --latest \
  --notes "Two fixes to 0.25.0: a value option spelled in camel case, such as --generatedBy, is refused instead of recording provenance for an actor named true (#262); cst --help describes --engine native as it behaves (#271). See CHANGELOG.md, section 0.25.1."

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

Step 3: verify an install each way (agent)

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.1
./npm-prefix/bin/cst --version

Expected: causet 0.25.1 from both. A refusal that names a SHA-256 mismatch means the release's assets and SHA256SUMS disagree; stop and record it.

Completion evidence

Attach to #274: 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 #274, set its board card to Done, and point the Human TODO entry at the completed outcome.

Clone this wiki locally