Drop Node.js 18 support #1317
Merged
Drop Node.js 18 support #1317
Conversation
This file contains 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
rowanmanning
requested review from
next-team,
ft-dependency-auto-merger and
a team
as code owners
CyntiBinti
approved these changes
Jan 20, 2025
Node.js 18 goes end-of-life in April. We can release major versions ahead of then - people can switch early if their apps are already running on Node.js 20+
rowanmanning
force-pushed
the
drop-node-18
branch
from
fbc7b9e to
12dd501
Compare
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.
Node.js 18 goes end-of-life in April. We can release major versions ahead of then - people can switch early if their apps are already running on Node.js 20+. I decided not to roll any further breaking changes into this release as I wanted the upgrade path to be simple and possible to be automated.