Narrow supported Node.js versions range to currently-out-versions #432
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
This is to prevent the expectation that this package will be compatible with a to-be-released Node.js version. When a new Node.js version comes out, it can be added to the list of supported versions as a new feature.
This was referenced Oct 8, 2022
This was referenced Jan 23, 2023
Merged
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 is to prevent the expectation that this package will be compatible with a to-be-released Node.js version. When a new Node.js version comes out, it can be added to the list of supported versions as a new feature.
This way, the supported releases always align with the compatibility tested releases.
What about Node.js v11, v13, v15, and v17?
These are all intermediate release that no-one should be using after the even release following it has come out. Any users currently using any of these should immediately upgrade to at least the next even release.
That being said, I'm happy to patch support for any of these back into the v1 release line on demand.
Relates to #193