Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 4 of node.js has been deprecated #10

Open
greenkeeper bot opened this issue May 22, 2018 · 0 comments
Open

Version 4 of node.js has been deprecated #10

greenkeeper bot opened this issue May 22, 2018 · 0 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented May 22, 2018

Version 4 of Node.js (code name Argon) has been deprecated! 馃殤

This means that it is no longer maintained and will not receive any more security updates. Version 6 (Boron) is now the lowest actively maintained Node.js version.
To see what effect this update from 4 to 6 would have on your code, Greenkeeper has already created a branch with the following changes:

  • The engines config in 1 of your package.json files was updated to the new lowest actively supported Node.js version

If you鈥檙e interested in removing support for Node.js 4 from this repo, you can open a PR with these changes.

You can find out more about the deprecation and possible update strategies in this Node.js foundation announcement.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • In engines, any occurance of 4 was replaced with 6
  • .nvmrc was updated to Node.js 4
  • .travis.yml was only changed if there was a root-level node_js key that specified Node.js 4. In this case, 4 was replaced with 6. We didn鈥檛 touch job or matrix configurations because these tend to be quite specific and complex, and it鈥檚 difficult to infer what the intentions were.

For many simpler .travis.yml configurations, these changes should already suffice, but depending on what you鈥檙e doing it may require additional work or may not be applicable at all. We鈥檙e also aware that you may have good reasons to continue supporting Node.js 4, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I鈥檓 a humble robot and won鈥檛 feel rejected 馃


FAQ and help

There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 馃尨

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants