ci: bump Node to 24 to fix release workflow#170
Merged
Conversation
The pre-cached npm 10.9.7 in Node 22.22.2 toolcache has a broken module tree (missing promise-retry), which makes `npm i -g npm@latest` fail with MODULE_NOT_FOUND. Upgrading to Node 24 ships npm 11.x with OIDC (trusted publishing) support, so the global npm upgrade step is no longer needed. Refs: - actions/runner-images#13883 - nodejs/node#62425 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ikawaha
approved these changes
Apr 24, 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.
Summary
engines.nodefrom22.xto24.xnpm i -g npm@latestfrom the publish workflow (no longer needed)Why
The Publish npm packages workflow has been failing since #160 (April 6) with:
Root cause is a known regression in the Node 22.22.2 toolcache image: the bundled npm 10.9.7 has a broken dependency tree (missing
promise-retry), so any command that triggers@npmcli/arborist— includingnpm i -g npm@latest— fails immediately.Node 24 (current Active LTS) ships npm 11.x which already supports trusted publishing (OIDC), so the global npm upgrade step becomes unnecessary.
Refs:
promise-retry) actions/runner-images#13883