Repository navigation
Pin the release npm self-update to major 11 - #6003
Merged
Merged
Conversation
…s missing `sigstore` and breaks `npm publish`
|
Fix in npm https://github.com/npm/cli/releases/tag/v12.0.1, see npm/cli#9740 |
akashchamp
pushed a commit
to akashchamp/drizzle-orm
that referenced
this pull request
Sep 25, 2026
Pin the release npm self-update to major 11
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
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.
The rc5 dispatch failed in
run-feature / release (drizzle-orm)withCannot find module 'sigstore'fromlibnpmpublish/lib/provenance.js(https://github.com/drizzle-team/drizzle-orm/actions/runs/29099638299).Root cause: npm 12.0.0 was just published as
latest, and its tarball is missingsigstorefrom the flattenednode_modulestree (it only exists underworkspaces/libnpmpublish/node_modules/, which isn't on the require path). Sinceprovenance.jsis loaded unconditionally, everynpm publishfails —--no-provenancedoesn't help. Verified by inspecting the tarballs:npm-12.0.0.tgzhas zeropackage/node_modules/sigstore/entries,npm-11.18.0.tgzhas them.Fix: pin the
Update NPMstep tonpm@11(currently 11.18.0) in both feature-branch release workflows. The>= 11.5.1trusted-publishing requirement still holds; the pin can move to 12 once upstream ships a fixed tarball.