Skip to content

ci: pin npm to the 11.x major in publish-npm — npm@latest broke provenance - #4

Merged
BrianLeishman merged 1 commit into
masterfrom
ci/pin-npm-11
Jul 8, 2026
Merged

BrianLeishman merged 1 commit into
masterfrom
ci/pin-npm-11

Conversation

@BrianLeishman

Copy link
Copy Markdown
Member

The v0.2.2 release's publish-npm job failed twice with "Cannot find
module 'sigstore'" from libnpmpublish's provenance path after
npm install -g npm@latest over Node 22's bundled npm. Trusted
publishing needs npm >= 11.5, so pin the known-good major instead of
tracking latest.

Co-Authored-By: Claude Fable 5 (1M context) noreply@anthropic.com

…nance

The v0.2.2 release's publish-npm job failed twice with "Cannot find
module 'sigstore'" from libnpmpublish's provenance path after
`npm install -g npm@latest` over Node 22's bundled npm. Trusted
publishing needs npm >= 11.5, so pin the known-good major instead of
tracking latest.

Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>
@BrianLeishman
BrianLeishman merged commit c11fcbb into master Jul 8, 2026
4 checks passed
@BrianLeishman
BrianLeishman deleted the ci/pin-npm-11 branch July 8, 2026 22:04
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