(ci) Stop explicitly using the latest npm - no longer needed#17408
Merged
Conversation
Removed the step to update NPM to the latest version.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR simplifies the npm publish GitHub Actions workflow by removing the step that force-upgraded npm to latest, relying instead on the npm version bundled with Node.js 24 (to avoid a known npm CLI regression and keep Trusted Publishing working).
Changes:
- Removed the
npm install -g npm@lateststep from the release publish workflow.
dkamburov
approved these changes
Jul 10, 2026
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.
Removed the step to update NPM to the latest version. Node 24 ships with a good enough version of npm in order to make Trusted Publishing to npmjs.org work.
Closes #
N/A
Description
Having this step was mandatory for node 20 and earlier builds of 22, but 24 ships a good enough node cli client.
Motivation / Context
The latest compatible version of the npm cli client ships with a show-stopper bug right now: npm/cli#9722 and we want to avoid hitting it.
Type of Change (check all that apply):
Component(s) / Area(s) Affected:
N/A
How Has This Been Tested?
N/A
Test Configuration:
N/A
Screenshots / Recordings
N/A
Checklist:
feature/README.MDupdates for the feature docsREADME.MDCHANGELOG.MDupdates for newly added functionalityng updatemigrations for the breaking changes (migrations guidelines)