Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update from node16 to node20 #392

Merged
merged 6 commits into from
Oct 28, 2023
Merged

Update from node16 to node20 #392

merged 6 commits into from
Oct 28, 2023

Conversation

korthout
Copy link
Owner

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.

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.
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.
@korthout korthout merged commit 1f42167 into main Oct 28, 2023
1 check passed
@korthout korthout deleted the korthout-node20 branch October 28, 2023 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant