ci: stop updating npm during release#554
Merged
Merged
Conversation
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
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
Remove the release workflow step that globally upgrades npm with
npm install -g npm@latestbefore running Changesets publish.Why
The failed release run for #544 reached the publish phase, but npm's provenance path failed with
MODULE_NOT_FOUND Cannot find module 'sigstore'after the workflow replaced the runner-provided npm installation. The Node 24 runner already provides npm 11.16.0, which is provenance-capable, so the global npm replacement is unnecessary and appears to be the source of the broken npm dependency tree.