Skip to content

chore: drop unsupported node versions #4447

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

Merged
merged 4 commits into from
Jul 2, 2025
Merged

Conversation

yaacovCR
Copy link
Contributor

@yaacovCR yaacovCR commented Jul 2, 2025

we will test only versions that are not EOL: i.e. 20, 22, 24, and update the engines field to those same versions give warnings on anything below 20.

we may further choose to require minimum subversions of 20, 22, and 24 that enable require(esm), but this PR holds off on that just yet.

@yaacovCR yaacovCR requested a review from a team as a code owner July 2, 2025 10:34
@yaacovCR yaacovCR added the PR: breaking change 💥 implementation requires increase of "major" version number label Jul 2, 2025
@yaacovCR yaacovCR merged commit 9b7e529 into graphql:next Jul 2, 2025
16 checks passed
@yaacovCR yaacovCR deleted the drop-old-node branch July 2, 2025 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: breaking change 💥 implementation requires increase of "major" version number
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants