CI Against Node 4.1#5067
Merged
Merged
Conversation
Perf isn't as bad as 0.12, and it's the new LTS release series. TBH, we should probably also CI against `'node'` for the latest public version.
Contributor
|
actually 4.2 will be LTS release nodejs/node#3000 (comment) |
Member
Author
|
Good to know. |
|
It's better to add "4" instead of "4.1" or "4.2". |
Member
Author
|
@mhegazy node 4.2 LTS has been released and the 4.x series is now slated to be supported for the next 30 months... maybe we should turn this on? |
Contributor
|
👍 |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
Perf isn't as bad as 0.12, and it's the new LTS release series. TBH, we should probably also CI against
'node'for the latest public version.