fix(ci): restore npm upgrade for OIDC provenance publishing - #14
Merged
Merged
Conversation
The bundled npm (v10.x) in Node 22 doesn't handle OIDC provenance publishing correctly with npm's trusted publishers. Restoring the npm@latest upgrade (now with corepack disable to avoid the promise-retry module error) to get npm v11.x which handles OIDC provenance properly.
alec-bell
force-pushed
the
fix/restore-npm-upgrade
branch
from
April 28, 2026 23:55
62abf5f to
429b632
Compare
Contributor
|
🎉 This PR is included in version 1.1.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Contributor
|
🎉 This PR is included in version 1.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Problem
npm publish with
--provenancehas been failing with 404 since PR #11 removed thenpm install -g npm@lateststep. The bundled npm v10.x in Node 22 doesn't handle OIDC provenance publishing correctly with npm's trusted publishers feature.Fix
Restore the npm@latest upgrade with
corepack disablefirst to prevent thepromise-retrymodule error that caused us to remove it in the first place.Context