Repository navigation
0.3.1 - published by the workflow, not by a token
The release path stopped carrying a secret.
0.3.0 was published from a laptop with a granular access token that had 2FA bypass
enabled, because the account's only second factor is a security key and npm publish
answers EOTP and exits rather than waiting for a web flow. That token has been
revoked, and npm ends direct publishing with bypass-2FA tokens in January 2027 anyway.
This version was published by .github/workflows/release.yml through Trusted
Publishing. The job asks for an OIDC identity, npm trades it for a short-lived
credential of its own, and provenance attaches without being asked: 0.3.1 carries a
SLSA provenance statement recorded in the Sigstore transparency log. There is no
NPM_TOKEN anywhere in the repository, and a test asserts that neither it nor
NODE_AUTH_TOKEN nor --provenance appears in the workflow.
The gate is the same shape the neighbouring repositories use. A release is dispatched
from the Actions tab against an audited SHA and refuses to run if main moved since,
refuses to run from anywhere but main, is dry-run by default, and requires ci to
have passed for that exact commit under main's own push event — a pull-request run
tested a merge ref under a different trigger and does not qualify. It fails closed when
the tag, the GitHub release, or the registry version already exists, since a published
version is immutable and a repointed tag rewrites what a release means.
No behaviour changed for anyone using the package. The only shipped difference is the
version string.
Known rough edge, fixed after this run: the workflow tagged with git tag -a without
setting a committer, so the tag step failed on a runner that has no git identity — after
the publish had already succeeded. This tag was created by hand at the same commit. The
registry also took several minutes to serve 0.3.1 after npm acknowledged the publish, so
the post-publish check now waits long enough to tell a slow registry from a failed one.