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

feat: allow Node 22 #831

Merged
merged 1 commit into from
Jun 14, 2024
Merged

feat: allow Node 22 #831

merged 1 commit into from
Jun 14, 2024

Conversation

alexmuller
Copy link
Member

People can use this now if they want to.

https://github.com/nodejs/release

People can use this now if they want to.

https://github.com/nodejs/release
@alexmuller alexmuller requested review from a team as code owners June 14, 2024 15:41
@alexmuller alexmuller merged commit 76f2894 into main Jun 14, 2024
13 checks passed
@alexmuller alexmuller deleted the allow-node-22 branch June 14, 2024 15:43
@joelcarr
Copy link
Member

What should our Node version policy be? Should packages support the current version as well or should we limit it to LTS versions?

@alexmuller
Copy link
Member Author

Not 100% sure on this but my gut feeling is that we should test on and support the latest we realistically can. That way by the time people come to upgrade their systems they hopefully won't get that many npm warnings because they'll already be on a package version with support.

But @rowanmanning has thought more about this than me.

@alexmuller
Copy link
Member Author

Sorry I should have added the context for this change - Ads tried to see if they could jump straight to 22 and it was fine except for this alert. So let's not hold them back if they want to be cutting edge testers for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants