Skip to content
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.

Update all dependencies 🌴 #1089

Merged
merged 1 commit into from
Aug 16, 2016
Merged

Update all dependencies 🌴 #1089

merged 1 commit into from
Aug 16, 2016

Conversation

greenkeeperio-bot
Copy link
Contributor

@greenkeeperio-bot greenkeeperio-bot commented Aug 15, 2016

Hello lovely humans,

welcome to automated dependency management with Greenkeeper.
To take full advantage of this service I recommend to start out with up-to-date dependencies.

I just updated all the dependencies in the package.json file in one go.
Please look into these changes and make sure your project still works with them applied.
If you can’t update everything right now that’s fine as well.
We’ll get there over time.

Now that you told me to monitor this project 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, 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 the caret ^ character .
When there is a failure reported for the update I’ll create a pull request so you know about the problem immediately. When it reports success I’ll delete the branch again, because no action needs to be taken – everything is fine.

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 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 right away.

Now you 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 :shipit:

Are you unsure about how things are supposed to work?

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 ✨

🌴


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade


This change is Reviewable

@@ -11,8 +11,8 @@
"classnames": "2.2.5",
"fancy-dedupe": "0.1.0",
"get-youtube-id": "1.0.0",
"history": "2.1.2",
"lodash.debounce": "4.0.7",
"history": "3.0.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change will fail due to needing an update of react-router which hasn't been published yet (remix-run/react-router#3611). I'll update the branch once the first pass of tests have run.

@Standard8 Standard8 force-pushed the greenkeeper-update-all branch from adad735 to d9a284c Compare August 15, 2016 18:17
@coveralls
Copy link

coveralls commented Aug 15, 2016

Coverage Status

Coverage remained the same at 92.18% when pulling d9a284c on greenkeeper-update-all into 1aadf9c on master.

@Standard8
Copy link
Member

This is ready for review now.

@pdehaan
Copy link
Collaborator

pdehaan commented Aug 16, 2016

LGTM, but not sure who needs to sign off on these module updates.
But I think this is blocking #1093 and #1094 PRs.

@k88hudson k88hudson self-assigned this Aug 16, 2016
@k88hudson
Copy link
Contributor

I'll take a look

@k88hudson
Copy link
Contributor

Looks good to me!

@k88hudson k88hudson merged commit 4915551 into master Aug 16, 2016
@k88hudson k88hudson deleted the greenkeeper-update-all branch August 16, 2016 18:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants