Repository navigation
Move CI and releases to Node 24 - #104
Conversation
The release job ran on Node 20 and then installed npm@latest to get the npm 11.5.1+ that trusted publishing needs. npm@latest is now npm 12, which requires Node ^22.22.2, ^24.15.0 or >=26, so the install failed with EBADENGINE. Node 24 bundles npm 11.19, so run the release job on 24.x and check the bundled npm is new enough instead of upgrading it. That keeps a future npm major from breaking the release the same way. The PR checks move to 24.x too, so tests run on the Node that publishes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017Rd4bUBQBDtzvj2wiHWZVk
|
kevinb-khan
left a comment
There was a problem hiding this comment.
I thought I updated them all, but I guess I missed this one. Thanks for updating the config to use Node 24. It should probably specify 24.22.1 or higher until we've confirmed that the version of node installed when you select 24.x is 24.22.1 or higher. The last time I checked, GitHub was still installing a lower version for some reason.
I checked the logs. It's using |
Summary:
The release job ran on Node 20 and then installed npm@latest to get the
npm 11.5.1+ that trusted publishing needs. npm@latest is now npm 12,
which requires Node ^22.22.2, ^24.15.0 or >=26, so the install failed
with EBADENGINE.
Node 24 bundles npm 11.19, so run the release job on 24.x and check the
bundled npm is new enough instead of upgrading it. That keeps a future
npm major from breaking the release the same way. The PR checks move to
24.x too, so tests run on the Node that publishes.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_017Rd4bUBQBDtzvj2wiHWZVk
Issue: FEI-8793
Test plan: