fix(ci): remove npm@latest upgrade in release workflow#434
Merged
Conversation
The release workflow ran `npm i -g npm@latest` before installing dependencies, silently picking up whatever npm CLI version was newest each run. A recent npm release added a new default restriction (EALLOWGIT) blocking git-protocol dependencies, breaking `npm i` for this repo's semantic-release-github-pullrequest devDependency (a git fork reference) and blocking every release since (including the 6.6.2 dependency bump in #433). No engines.npm pin here, so just drop the forced upgrade and let actions/setup-node's bundled npm run the install.
jairo-bc
marked this pull request as ready for review
July 14, 2026 08:56
rtalvarez
approved these changes
Jul 14, 2026
Contributor
|
🎉 This PR is included in version 5.4.3 🎉 The release is available on: 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.
What? Why?
npm i -g npm@latestbefore install, picking up whatever npm CLI is newest each runEALLOWGIT) blocking git-protocol dependenciessemantic-release-github-pullrequestdevDependency points at a git fork — install now fails, blocking every release since (including the 6.6.2 dependency bump in fix(deps): bump @bigcommerce/stencil-paper-handlebars to 6.6.2 #433)engines.npmpin — just drop the forced upgrade, letactions/setup-node's bundled npm run installHow was it tested?