Greenkeeper

🤖 BEEP. IMPORTANT MESSAGE FOLLOWS. Greenkeeper has teamed up with @snyksec! Together, we’re building a new generation of dependency update service that’s an integral part of Snyk (snyk.io). This will bring about a few changes in the near future: 🧵

And here we have it. @greenkeeper is ceasing operations as of today. We’re thanking all our loyal customers and open source users for their trust since 2015. Goodbye 🤖🌴

To migrate over to Snyk, and for way more info on this, please visit greenkeeper.io Our heartfelt thanks to all of you who’ve been a part of Greenkeeper, one way or the other, since we started five years ago. BEEP BOOP. KEEP IT GREEN 💚 GK OUT 👋🤖🌴

In short, this will change: 🌴 Greenkeeper shuts down on the 3rd of June 🌴 No more new signups, from today 🌴 Existing users can migrate to Snyk’s free plan (more generous than ours!) 🌴 We’re not forcing you to migrate, you’re free to use GK until it shuts down

In 2015, Greenkeeper was one of the first dependency update services. In the last year, dependency updates finally arrived in the mainstream: on platform level, and as part of larger services. We realised that we also needed a larger partner to keep up with this development.

We’ll stop Greenkeeper’s operation as an independent service on the 3rd of June 2020. However, we’ve made it easy for you to migrate your repositories over to the good folks at Snyk (snyk.io).

🤖 BEEP. IMPORTANT MESSAGE FOLLOWS. Greenkeeper has teamed up with @snyksec! Together, we’re building a new generation of dependency update service that’s an integral part of Snyk (snyk.io). This will bring about a few changes in the near future: 🧵

remembers the day @greenkeeperio was announced and, shortly after, turning it on before there was even much of a UI for it. Good night, greenkeeper, for y'all were totally able to change the conversation on upstream dependencies.

Neighbourhoodie says Goodbye to @greenkeeperio and hello to @snyksec. Together, we’ll deliver the next generation in developer tooling: neighbourhood.ie/blog/2020/03/0…

We're excited to share news about our partnership with @neighbourh00die, the makers of Greenkeeper, to help developers proactively maintain dependency health via automated dependency upgrades. More about this here: buff.ly/2x5yZ8E @greenkeeperio #DevSecOps

We’ve been working hard with the team and @greenkeeperio to make this happen and finally it’s official! 💜💚 snyk.io/blog/snyk-part…

@zephilim that’s it!

@greenkeeperio I'm only wanting to get the basic info without having to guess or make assumptions. So let's breakdown what you said above. When you say branch, you mean the GK branch. So I check out the GK branch locally, fix the issue there. Then commit and push the changes back ...

@greenkeeperio Hi, I've just seen my GK pull-request for an dependeny update that break s the build. Problem is, I don't know how to properly handle the pull request. Do you have any documentation that explains in detail what I'm supposed to do to handle the pull request? (1/2)..

@zephilim 2. ignore the PR until a new version of the dependency comes out that maybe hopefully fixes the issue. 2/2. You might also want to look at the release notes of the dependency release to see if they mention anything about breaking changes.