Skip to content

ci: pin publish-step npm to the 11.x line#14

Merged
jaymaycry merged 1 commit into
mainfrom
ci/pin-npm-11-publish
Jul 10, 2026
Merged

ci: pin publish-step npm to the 11.x line#14
jaymaycry merged 1 commit into
mainfrom
ci/pin-npm-11-publish

Conversation

@jaymaycry

Copy link
Copy Markdown
Contributor

The v0.4.0 publish failed: the workflow upgrades to npm@latest, which is now npm 12.0.0, and its libnpmpublish dies with MODULE_NOT_FOUND: sigstore on the OIDC/provenance path. Node 24 already bundles npm 11.16.0 (≥ the 11.5.1 Trusted Publishing floor), so this pins the upgrade to the 11.x line.

The v0.4.0 republish was dispatched from this branch (workflow_dispatch with publish_tag=v0.4.0 checks out the tag for the actual build), so merging this is only needed for future releases, not for 0.4.0.

🤖 Generated with Claude Code

https://claude.ai/code/session_012rn1KYa8uH8ikwK3AaHaLP

npm 12.0.0 (current latest) fails `npm publish` under OIDC Trusted
Publishing with MODULE_NOT_FOUND on 'sigstore' in libnpmpublish's
provenance path — this is what broke the v0.4.0 publish. Node 24's
bundled npm is already 11.16.0, so 11.x comfortably clears the
>= 11.5.1 Trusted Publishing floor.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012rn1KYa8uH8ikwK3AaHaLP
@jaymaycry jaymaycry mentioned this pull request Jul 10, 2026
@jaymaycry jaymaycry merged commit 00185ed into main Jul 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant