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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

👻😱 Node.js 0.10 is unmaintained 😱👻 #2115

merged 1 commit into from Jan 11, 2017


Copy link

🎃 Happy Halloween from Greenkeeper 🎃

Node.js 0.10 Jack O Lantern
Generated with MakeSweet

Have you heard the news?
💀Node.js 0.10 is no longer maintained💀
Up until today it used to receive critical bug and security fixes, but these times are over for good.

Node.js LTS schedule

Node.js 0.10 is definitely not alive, but it’s also not dead yet. Its ghost is still haunting the Node.js community 👻 Many open source projects still support it, and yours is among them.
In order for the Node.js community to evolve we have to say goodbye to Node.js 0.10. It’s time for us to finally send it to the realm of the dead.

With this pull request I have removed all deprecated versions of Node.js from your project. I suggest supporting all versions of Node.js that are greater than 4 (Node.js 0.12 will be unmaintained by the end of the year as well). Please review this properly and help us to rout the Ghost of Node.js 0.10 👻💀 Of course you can just close this pull request and keep supporting Node.js 0.10 … but … you have been warned … it’s scary to deal with the living dead 😨

Good luck, your Greenkeeper Bot 🎃

Greenkeeper Integration Screencast

One more thing …

As we’re already replacing old things with their newer and better versions: There is an all new Greenkeeper. It’s based on GitHub Integrations, with first class bot support.
I promise, it’s not spooky at all 🎃

BREAKING CHANGE: This module no longer supports Node.js 0.10
@ryanseddon ryanseddon merged commit 70c19b3 into master Jan 11, 2017
@ryanseddon ryanseddon deleted the greenkeeper/remove-node-0.10 branch January 11, 2017 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

3 participants