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

chore!: drop support for Node.js 21 #15118

Merged
merged 3 commits into from
Jul 12, 2024
Merged

chore!: drop support for Node.js 21 #15118

merged 3 commits into from
Jul 12, 2024

Conversation

mrazauskas
Copy link
Contributor

Summary

Perhaps it is time to drop Node.js 21? It is end-of-life since 2024-06-01. Reference: https://github.com/nodejs/Release

Test plan

Green CI.

Copy link

netlify bot commented Jun 10, 2024

Deploy Preview for jestjs ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 4a247ef
🔍 Latest deploy log https://app.netlify.com/sites/jestjs/deploys/6667f32139e1c40008269226
😎 Deploy Preview https://deploy-preview-15118--jestjs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -24,7 +24,8 @@ describe('Wrong globals for environment', () => {
assertFailuresAndSnapshot(['node', '-t=document']);
});

onNodeVersions('<21', () => {
// Node.js 18 is the last LTS version, which is missing the global 'navigator'
onNodeVersions('<=18', () => {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test will be obsolete after dropping Node.js 18. So I though, perhaps keeping 18 here makes it easier to notice that?

@mrazauskas
Copy link
Contributor Author

@SimenB Could you take a look, please? GHA is waiting for status checks on Node v21.x, because these are marked as required. Not so easy to remove them (;

@SimenB
Copy link
Member

SimenB commented Jul 12, 2024

Not sure about this. It would mean people supporting >=20 wouldn't be able to use Jest. Same technically applies to >=18 already as we've dropped 19, so maybe not a big deal? And as long as we do support 18 (and 16 for that matter), the likelihood of those breaking are low.

So yeah, I think I convinved myself 😀

@SimenB SimenB merged commit 697ce45 into jestjs:main Jul 12, 2024
73 checks passed
@mrazauskas mrazauskas deleted the drop-nodejs-21 branch July 12, 2024 08:40
@mrazauskas
Copy link
Contributor Author

I think that is fine, since Node.js does not recommend the odd versions for production anyways. Play with it, have fun, but that is it.

Copy link

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants