Update from node16 to node20 #392
Merged
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
New changes will break backward compatibility because we'll drop support for node16 in favor of node20, like most actions. While this doesn't affect most users, it's a breaking change nevertheless, which is why we'll move to v2. After this, the v1.next-preview tag will no longer be updated. Users using main directly will immediately update. Users that want to be explicit about the major version but want the latest (unreleased) changes can use v2.next-preview from now on.
Node16 has reached end-of-life and is no longer supported. See: https://github.com/nodejs/release#release-schedule See: https://nodejs.org/en/blog/announcements/nodejs16-eol
This allows us to specify node20 in the ci.
This step existed to update the release-next-preview workflow, but that workflow was rolled into the main ci workflow.
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.
This is needed because node16 is end-of-life.
See: https://github.com/nodejs/release#release-schedule
See: https://nodejs.org/en/blog/announcements/nodejs16-eol
Since this drops support for node16, it is a breaking change and requires us to move to
v2.