Update dependencies to enable Greenkeeper 🌴 #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let’s get started with automated dependency management for clock-timer.js 💪
This pull request updates all your dependencies to their latest version. Having them all up to date really is the best starting point. I will look out for further dependency updates and make sure to handle them in isolation and in real-time, as soon as you merge this pull request.
I won’t start sending you further updates, unless you have merged this very pull request.
🏷 How to check the status of this repository
There is a badge added to your README, indicating the status of this repository.This is how your badge looks like 👉![Greenkeeper badge](https://camo.githubusercontent.com/159dc0828f07278b9e8bbbbeb043ef1e530e4a27689581a95d5a24936635da56/68747470733a2f2f6261646765732e677265656e6b65657065722e696f2f67616d65737464696f2f636c6f636b2d74696d65722e6a732e737667)
👩💻 How to update this pull request
🙈 How to ignore certain dependencies
In case you can not, or do not want to update a certain dependency right now, you can of course just change the
package.json
file back to your liking.Add a
greenkeeper.ignore
field to yourpackage.json
, containing a list of dependencies you don’t want to update right now.✨ How the updates will look like
As soon as you merge this pull request I’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.
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 the caret^
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.
In this example the new version
4.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.
Now you no longer need to check for exciting new versions by hand – I’ll just let you know automatically.![:shipit: :shipit:](https://github.githubassets.com/images/icons/emoji/shipit.png)
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
💁♂️ Not sure how things are going to work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Good luck with your project and see you soon ✨
Your Greenkeeper Bot 🌴