ci: run on node 24 - #26
Merged
Merged
Conversation
The workflows and the `.tool-versions` pin move to node 24; the published `engines` stay at `>=22`.
Contributor
Coverage Report for CI Build 33511755893Coverage remained the same at 93.692%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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.
Moves development and CI from node 22 to node 24: the
.tool-versionspin and everynode-versionin the workflows —checks.yml,commit.yml,tests.ymlandrelease.yml.All eleven packages were run on 24 before this: core 105, bundler-utils 37, cli 46, loader 49, vite-plugin 27, runtime 20, react 16, preact 17, svelte 16, cloudflare 32, imgproxy 30 — plus
tsc --noEmitand oxlint per package. The native pieces are fine: sharp resolves its prebuilt binary through N-API, and the.tssources still run under node's own type stripping.The published
enginesare deliberately left at>=22: raising them is a breaking change for consumers, and it belongs in its own release-visible commit. Worth deciding separately, though — with nothing running on 22 any more, the claim stops being tested.