Push the changes to this branch and merge it.

This is how your badge looks like 👉

In case you can not, or do not want to update a certain dependency right now, you can of course justchange thepackage.json file back to your liking.

Add agreenkeeper.ignore field to yourpackage.json, containing a list of dependencies you don’t want to update right now.

// package.json{…"greenkeeper":{"ignore":["package-names","you-want-me-to-ignore"]}}

As soon as you merge this pull requestI’ll create a branch for every dependency update, with the new version applied. The branch creation should trigger your testing services to check the new version. Using the results of these tests I’ll try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date.

-  "underscore": "^1.6.0"+  "underscore": "^1.7.0"

In the above example you can see an in-range update.1.7.0 is included in the old^1.6.0 range, because of thecaret^ character.
When the test services report success I’ll delete the branch again, because no action needs to be taken – everything is fine.
When there is a failure however, I’ll create an issue so you know about the problem immediately.

This way every single version update of your dependencies will either continue to work with your project, or you’ll get to know of potential problems immediately.

-  "lodash": "^3.0.0"+  "lodash": "^4.0.0"

In this example the new version4.0.0 is not included in the old^3.0.0 range.
For version updates like these – let’s call them “out of range” updates – you’ll receive a pull request.

Nowyou no longer need to check for exciting new versions by hand – I’ll just let you know automatically.
And the pull request will not only serve as a reminder to update. In case it passes your decent test suite that’s a strong reason to merge right away

There is a collection offrequently asked questions and of course you may alwaysask my humans.