chore: drop unsupported node versions (#4447)

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

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.

---------

Co-authored-by: Benjie <benjie@jemjie.com>

Author: yaacovCR

.github/workflows/ci.yml

@@ -145,7 +145,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node_version_to_setup: [16, 18, 19]
+        node_version_to_setup: [20, 22, 24]
     permissions:
       contents: read # for actions/checkout
     steps:

.node-version

@@ -1 +1 @@
-v20
+v24

package-lock.json

@@ -26,7 +26,7 @@
     "graphql-js"
   ],
   "engines": {
-    "node": "^16.19.0 || ^18.14.0 || >=19.7.0"
+    "node": "^20.0.0 || ^22.0.0 || >=24.0.0"
   },
   "scripts": {
     "preversion": "bash -c '. ./resources/checkgit.sh && npm ci --ignore-scripts'",

package.json

@@ -12,6 +12,10 @@ import { Callout } from 'nextra/components'
 
 # Breaking changes
 
+## Required Node.js versions
+
+The v17 release drops support for end-of-life versions of Node.JS, retaining support for versions 20, 22, and 24 or above.
+
 ## Default values
 
 GraphQL schemas allow default values for input fields and arguments. Historically, GraphQL.js did not rigorously validate or coerce these