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

Update all dependencies 🌴 #484

Merged
merged 7 commits into from Feb 25, 2017

Conversation

Projects
None yet
2 participants
@greenkeeperio-bot
Copy link
Contributor

greenkeeperio-bot commented Feb 25, 2017

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

@helfer helfer added the greenkeeper label Feb 25, 2017

@helfer

This comment has been minimized.

Copy link
Member

helfer commented Feb 25, 2017

I decided to turn on greenkeeper for this repo. Not sure why we didn't have it before.

@helfer helfer force-pushed the greenkeeper-update-all branch from 790672f to 530674e Feb 25, 2017

@helfer

This comment has been minimized.

Copy link
Member

helfer commented Feb 25, 2017

Alright, apart from mobx, everything still seems to work with a bit of fiddling 🎉

I'll open a separate PR for updating mobx.

@helfer helfer merged commit ee90601 into master Feb 25, 2017

5 checks passed

./dist/index.min.js +357 bytes (+1.27%) → 28,043 bytes
CLA Author has signed the Meteor CLA.
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 93.945%
Details

@calebmer calebmer deleted the greenkeeper-update-all branch Feb 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment