feat: Deprecate support for Node.js 6.x.x #3579
Merged
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.
As Node.js 6.x.x is in maintenance mode, we deprecate support for it. We'll keep it deprecated until the usage of it is very low.
Disable support for Node.js 4.x.x and 5.x.x
Currently, when CLI is used with Node.js 4.x.x or 5.x.x, a warning has been shown. As we are deprecating support for Node.js 6.x.x and Node.js 4.x.x is near the end of its life, remove the support for Node.js versions below 6.x.x
In case Node.js 4.x.x is used, CLI will show error and will not execute the command. Node.js 4.x.x has been deprecated for some months.
PR Checklist
What is the current behavior?
CLI allows using Node.js 4, 5, 6. In case Node.js 4.x.x or 5.x.x is used, CLI prints a warning on each command.
What is the new behavior?
CLI does not allow using Node.js 4.x.x and 5.x.x - each command fails immediately.
In case Node.js 6.x.x is used, CLI prints warning that support for Node.js 6.x.x is deprecated.
Implements #3581 and #3582