fix: drop support for node 13#10685
Conversation
| }, | ||
| "engines": { | ||
| "node": ">= 10.14.2" | ||
| "node": "^10.13.0 || ^12.13.0 || ^14.14.0 || >=15.0.0" |
There was a problem hiding this comment.
match the first version of node 10, 12 and 14 marked as LTS
https://nodejs.org/en/blog/release/v10.13.0/
https://nodejs.org/en/blog/release/v12.13.0/
There was a problem hiding this comment.
14 will be 14.15 when that's released as LTS next week
|
I'll land this one first of the breaking ones, just to reduce CI runs 😅 So that means I'll start landing Tuesday or Wednesday, depending on when v14 LTS drops |
|
Planning to land tonight as long as no new issues that require patches pop up |
* master: (398 commits) chore(breaking): remove undocumented `enabledTestsMap` config (jestjs#10787) Change expect.not.objectContaining() to match documentation (jestjs#10708) chore: add name to root project (jestjs#10782) Added explanation on how to use custom @jest-environment to docs (jestjs#10783) fix: remove deprecated functions from the jest object (jestjs#9853) chore: convert jest-runtime to ESM (jestjs#10325) fix(resolve): use escalade to find package.json (jestjs#10781) feat(jest-runner): set exit code to 1 if test logs after teardown (jestjs#10728) chore: add `exports` field to all `package.json`s (jestjs#9921) fix: do not inject `global` variable into module wrapper (jestjs#10644) chore: migrate jest-resolve to ESM (jestjs#10688) chore(transform): refactor API to pass an options bag around rather than multiple boolean options (jestjs#10753) chore: default to node test env rather than browser (jestjs#9874) fix: drop support for node 13 (jestjs#10685) chore: show enhanced syntax error for all syntax errors (jestjs#10749) chore: update lockfile after publish v26.6.3 chore: update changelog for release Don't throw an error if mock dependency can't be found (jestjs#10779) chore: bump babel core types (jestjs#10772) ...
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
3 participants
Summary
This changes our engine ranges to match the first version of node 10, 12 and 14 marked as LTS (14 will become LTS Oct. 27 - for now I just put the current release). In addition, v15 or newer is also within range.
This removes v11 (which we haven't been testing on CI anyways) and v13 entirely from the engine range, and removes v13 from CI as that was EOL in June.
This is actually lowering the minimum version of v10 since we don't need that specific version anymore (
vm.compileFunctionwas removed in #10586)Test plan
Green CI