Skip to content

Move workflows to Node 24.15.0 — 22.22.2 toolcache ships a broken npm#24

Merged
yosriady merged 1 commit into
mainfrom
fix/release-node-24
Jul 24, 2026
Merged

Move workflows to Node 24.15.0 — 22.22.2 toolcache ships a broken npm#24
yosriady merged 1 commit into
mainfrom
fix/release-node-24

Conversation

@yosriady

@yosriady yosriady commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #23. The release run on Node 22.22.2 failed again at npm install -g npm@latest, this time because the 22.22.2 build in the Actions hosted toolcache bundles a broken npm — its own dependency tree is missing promise-retry:

npm error code MODULE_NOT_FOUND
npm error Cannot find module 'promise-retry'
npm error - /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/rebuild.js

Every npm install fails at require time on that image, so the bundled npm can't even bootstrap its own upgrade. Rather than working around a corrupted toolcache build, this moves both workflows to Node 24.15.0 — the active LTS, explicitly supported by npm 12 (^24.15.0), with a healthy bundled npm.

Test plan

  • CI passes on this PR (build + tests on Node 24)
  • After merge, re-point the v1.1.0 tag at the new main head and confirm the release workflow's npm install -g npm@latest step succeeds

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

The Node 22.22.2 build in the GitHub Actions hosted toolcache bundles
an npm whose own dependency tree is incomplete (MODULE_NOT_FOUND:
promise-retry inside @npmcli/arborist), so every npm install — including
the npm self-upgrade needed for trusted publishing — fails at require
time. Node 24.15.0 is the active LTS, is explicitly supported by npm 12
(^24.15.0), and has a healthy bundled npm.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@yosriady
yosriady merged commit 837a4da into main Jul 24, 2026
6 checks passed
@yosriady
yosriady deleted the fix/release-node-24 branch July 24, 2026 14:26
@yosriady yosriady mentioned this pull request Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant