Run Node 24 in CI and release - #36
Merged
Merged
Conversation
The release job pinned Node 20 and installed npm@latest. npm 12 requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, so the job started failing with EBADENGINE the day npm 12 became latest, blocking the release of the changesets already on main. Move both workflows to Node 24 and pin npm to 12 rather than tracking latest, so the release runtime is deterministic instead of breaking whenever npm raises its engine requirement. CI now pins Node too, so it matches the release job instead of drifting with the runner image.
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
1 participant
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.
The release job pinned Node 20 and installed
npm@latest. npm 12 requires Node^22.22.2 || ^24.15.0 || >=26.0.0, so it started failing withEBADENGINEthe day npm 12 becamelatest:That failure is currently blocking the release of the changesets already merged to main — npm is still on 1.3.0 and no Version Packages PR was created.
Changes
@latest, so the release runtime is deterministic instead of breaking whenever npm raises its engine requirement.Verified locally on Node 24.18.0 / npm 12: install, build, check, test and perf all pass.