Dropped support for Node 16

Node 16 will reach EOL no later than a few months after Jasmine 5 is
released. Experience with Node 12 and Node 14 has shown that our
dependencies, especially dev dependencies, move on from past-EOL Node
versions fairly quickly. That can make it difficult to continue supporting
them. Since long term support for past EOL Node versions is a non-goal and
many users expect that Node versions will only be dropped in major
releases, it's better to drop it in 5.0.

.circleci/config.yml

@@ -11,11 +11,6 @@ executors:
     docker:
       - image: cimg/node:18.0.0
     working_directory: ~/workspace
-  node16:
-    docker:
-      # Oldest version with reliable support for error cause property
-      - image: cimg/node:16.14.0
-    working_directory: ~/workspace
 
 jobs:
   test:
@@ -42,10 +37,7 @@ jobs:
       - checkout
       - run:
           name: Install Node.js
-          # 16.3.2 is possibly the newest Node 16.x version that's compatible
-          # with nvm for windows:
-          # See <https://stackoverflow.com/questions/70958371/unexpected-token-when-trying-to-run-npm-install>.
-          command: nvm install 16.14.0 && nvm use 16.14.0
+          command: nvm install 18.0.0 && nvm use 18.0.0
       - run:
           name: Report Node and NPM versions
           command: echo "Using Node $(node --version) and NPM $(npm --version)"
@@ -65,7 +57,6 @@ workflows:
             parameters:
               executor:
                 - node18
-                - node16
       - test_win
   cron:
     <<: *push_workflow

README.md

@@ -50,7 +50,7 @@ Jasmine is compatible with both ES modules and CommonJS modules. See the
 
 ## Node version compatibility
 
-Jasmine supports Node 18 and 16.14-16.19.
+Jasmine supports Node 18.
 
 ## Support