fix(ci): pin npm and make provenance explicit in npm publish#53
Merged
Conversation
The npm publish job crashed with 'Cannot find module sigstore' (MODULE_NOT_FOUND) inside npm's provenance code path. It tracked npm@latest, which grabbed a release whose bundled sigstore fails to load. With id-token: write set, npm auto-triggers provenance and hits the broken module. Pin npm to 11.6.2 (working sigstore) and pass --provenance explicitly so behavior no longer depends on npm auto-detecting the OIDC token.
ErikTech
approved these changes
Jul 10, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes the npm publish job crashing with
Cannot find module 'sigstore'(MODULE_NOT_FOUND).What was happening
The publish job tracked
npm@latest, which pulled a release whose bundledsigstoremodule fails to load. Withid-token: writeset, npm auto-triggers provenance generation, hits the broken module, and crashes mid-publish.Fix
11.6.2(workingsigstore, supports trusted publishing) instead of chasing@latest.--provenanceexplicitly on both publish steps so behavior no longer depends on npm silently auto-detecting the OIDC token.Provenance attestations are kept on.