ci: upgrade nodejs release to npm 12#7900
Merged
Merged
Conversation
Xuanwo
changed the title
dosubot
Bot
added
size:XS
PsiACE
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
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.
Which issue does this PR close?
Closes #7897.
Rationale for this change
The NodeJS release workflow was running on Node 20 while installing
npm@latest. During the 0.58.0 release,npm@latestresolved to npm 12, which requires a newer Node runtime and caused the publish job to fail.Instead of pinning the release workflow to an older npm major, this PR upgrades the NodeJS release workflow to run on Node 24 and installs npm 12 explicitly.
What changes are included in this PR?
npm@12in the publish job.node@20tonode@24.Are there any user-facing changes?
No.
AI Usage Statement
AI assistance was used to prepare this PR.