feat!: Require Node >=20.19.0 as minimum supported version#22558
Draft
andreiborza wants to merge 1 commit into
Draft
feat!: Require Node >=20.19.0 as minimum supported version#22558andreiborza wants to merge 1 commit into
>=20.19.0 as minimum supported version#22558andreiborza wants to merge 1 commit into
Conversation
Bumps the minimum supported Node.js version to 20.19.0 for v11 and removes now-dead runtime branches that guarded pre-20 Node versions. Ref #22056 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
size-limit report 📦
|
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
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.
What
Raise the minimum supported Node.js version to
20.19.0for v11.engines.nodeto>=20.19.0across all packages and dev-packages.diagnostics_channelrefcount fallbacks, and the redis!dc.tracingChannelfallback.ci-unit-tests.tsand refresh stale Node-18 references (issue template, workflow comment, docs, pino/spotlight docstrings).Why
v11 targets Node
20.19.0so the SDK can rely onrequire(esm)and stabletracingChannelwithout polyfills or legacy code paths. CI matrices, the migration guide, and the volta pin were already moved to Node 20; this aligns the publishedenginesfields and removes the dead code the old floor required.Kept the
>=22.12gates and the cross-runtime!dc.tracingChannelguards in@sentry/server-utils, which are still reachable on Deno/Bun/Cloudflare. The react-router server-OTel path and itsnode-20-18e2e apps are left to #22290, which removes them.Ref #22056