Allow node v20+ #549
Open
Allow node v20+ #549
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Does it matter? I think it'd help if you explain your use case. |
|
I have to work with some Ubuntu 20.04 servers that are stuck on node 20.5.1 for some reason. Corepack seems to be compatible with it, so it seems odd to arbitrarily require a specific minor release in the package.json |
|
It's not exactly arbitrary, Node.js 20.5.1 was a current release, and Node.js 20.10.0 was a LTS release. I would encourage you to upgrade, you're behind a few security releases. If we're making changes, we should also remove changes to Node.js 21.x, and remove the CI job. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was added in 9a1cb38 when dropping support for node v19, but I can't see any reason why for instance node v20.5.0 should be excluded.