CI: pin npm to 11 for publish (works around npm@12 sigstore bug)#3875
Merged
Conversation
The Publish package to npm with OIDC step runs npx npm@latest publish,
which currently resolves to npm@12.0.0. That version fails at publish
time with:
npm error code MODULE_NOT_FOUND
npm error Cannot find module sigstore
npm error Require stack:
npm error - .../npm/node_modules/libnpmpublish/lib/provenance.js
libnpmpublish requires sigstore for OIDC provenance but the module is
missing from npm@12s dependency tree. This blocks every canary publish
until either npm ships a fix or we pin to a working version. Pinning to
npm@11 is the minimal, reversible fix; revert once npm upstream resolves
this.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pins npm to
11in.github/workflows/shared-npm-publish.yaml.npm@latestcurrently resolves tonpm@12.0.0, which fails at publish withCannot find module 'sigstore'— this blocks every canary publish.The failure
Run #550 (manual dispatch,
2026.x @ c3c89622):Upstream issue:
libnpmpublishrequiressigstorefor OIDC provenance but the module is missing fromnpm@12's dependency tree.Fix
Minimal and reversible — revert the pin once npm upstream ships a fix.
Test plan
2026.x: dispatchFrontend build and publishand confirmcanary-publish / publishreachesnpm publishwithout thesigstoreerror, producing a new1.0.0-canary.*on npm.