Drop node version v6, add support to node v11 and v12 #803
Conversation
This file contains hidden or 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
Member
Author
I have mixed feelings about that, what do You prefer? |
Member
|
According to this, v9 is already EOL https://nodesource.com/blog/understanding-how-node-js-release-lines-work/ and v11 will be in a few months, so I'd say we remove 9 and we might even just concentrate on 8, 10 and 12 (but I also wouldn't mind including 11, it just feels obsolete compared to the two LTS releases and v12). |
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.
Release schedule
https://github.com/nodejs/Release