AgentSeal 832dd4ada1 fix(ci): upgrade npm to 11.5.1+ for OIDC trusted publishing ... Node 22 ships with npm 10.x, which does not know how to exchange the GitHub OIDC id-token for a short-lived npm token. Without this upgrade, the publish step silently falls back to the empty NODE_AUTH_TOKEN that setup-node writes to .npmrc, and the registry returns 404. First test publish (v0.7.4-rc.0) failed at exactly this point, even though provenance signing via sigstore succeeded, confirming the OIDC handshake with GitHub was fine and only the npm-side auth was broken. Fix: `npm install -g npm@latest` before the publish step. Adds ~5s to runtime.		2026-04-18 09:33:52 -07:00
..
workflows	fix(ci): upgrade npm to 11.5.1+ for OIDC trusted publishing	2026-04-18 09:33:52 -07:00
FUNDING.yml	v0.1.0 - initial release	2026-04-13 15:10:27 -07:00