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 😱👻 #924

Merged
merged 3 commits into from
Nov 6, 2016

Conversation

greenkeeperio-bot
Copy link
Contributor

🎃 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 🎃 github.com/integration/greenkeeper

@coveralls
Copy link

coveralls commented Oct 31, 2016

Coverage Status

Coverage remained the same at 97.583% when pulling 1b01480 on greenkeeper/remove-node-0.10 into 676822c on develop.

@bgriffith
Copy link
Member

Only half the job! Doesn't touch app veyor!

@DanPurdy
Copy link
Member

DanPurdy commented Nov 1, 2016

Interesting they're taking node 0.12 out too!

closes #896

I'm still in 2 minds whether further updates should be a v2 release after this? Breaking it on certain systems wouldn't be great if we start adding node > 4 features

greenkeeperio-bot and others added 2 commits November 2, 2016 00:19
BREAKING CHANGE: This module no longer supports Node.js 0.10
@coveralls
Copy link

coveralls commented Nov 2, 2016

Coverage Status

Coverage remained the same at 97.583% when pulling 32bc088 on greenkeeper/remove-node-0.10 into d67549d on develop.

@coveralls
Copy link

coveralls commented Nov 2, 2016

Coverage Status

Coverage remained the same at 97.583% when pulling 32bc088 on greenkeeper/remove-node-0.10 into d67549d on develop.

@DanPurdy DanPurdy added this to the 1.10 milestone Nov 3, 2016
@coveralls
Copy link

coveralls commented Nov 6, 2016

Coverage Status

Coverage remained the same at 97.54% when pulling 775ef96 on greenkeeper/remove-node-0.10 into 4cd8a98 on develop.

@DanPurdy DanPurdy merged commit b2f4228 into develop Nov 6, 2016
@DanPurdy DanPurdy deleted the greenkeeper/remove-node-0.10 branch November 6, 2016 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants