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

chore(package): 🌴 Update Dependencies 🚀🔃 💋 #93

Merged
merged 1 commit into from Jan 20, 2017

Conversation

Projects
None yet
2 participants
@greenkeeper

greenkeeper bot commented Jan 20, 2017

Let’s get started with automated dependency management for jali 💪

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.

If this pull request passes and everything is still working

This is really good news. Merge this pull request and I will keep you posted about dependency updates you shouldn’t miss.

If this pull request fails and things aren’t working

Note: I won’t start sending you further updates, unless you have merged this very pull request.

So, how do we proceed? I suggest you find out what dependency update is causing the problem. Adapt your code so things are working nicely together again. next-update is a really handy tool to help you with this.

Push the changes to this branch and merge it.

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.

Don’t forget to push your changes to this branch, and merge this pull request, so I can start sending you further updates.


How to update this pull request
# change into your repository’s directory
git fetch
git checkout greenkeeper/update-all
npm install-test
# adapt your code, so it’s working again
git commit -m 'chore: adapt code to updated dependencies'
git push origin greenkeeper/update-all
How to ignore certain dependencies

Add a greenkeeper.ignore field to your package.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"
    ]
  }
}
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.

-  "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 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 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.
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:

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 🌴

@CLAassistant

This comment has been minimized.

Show comment
Hide comment
@CLAassistant

CLAassistant Jan 20, 2017

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

CLAassistant commented Jan 20, 2017

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

@greenkeeper greenkeeper bot added the greenkeeper label Jan 20, 2017

@clavecoder clavecoder changed the title from Update dependencies to enable Greenkeeper 🌴 to chore(dependencies): 🌴 Update Dependencies 🔃 🔨 💋 Jan 20, 2017

@clavecoder clavecoder merged commit cfdeef7 into master Jan 20, 2017

5 of 7 checks passed

VersionEye There are all kind of security and license issues!
Details
licence/cla Contributor License Agreement is not signed yet.
Details
bitHound - Code No failing files.
Details
bitHound - Dependencies No failing dependencies.
Details
dependency-ci Dependencies checked
Details
greenkeeper/verify Greenkeeper verified pull request
Details
semaphoreci The build passed on Semaphore.
Details

@greenkeeper greenkeeper bot deleted the greenkeeper/update-all branch Jan 20, 2017

@clavecoder

This comment has been minimized.

Show comment
Hide comment
@clavecoder

clavecoder Jan 20, 2017

Member
  • "@types/node": "^6.0.60",
  • "@types/node": "^7.0.0",
  • "esdoc": "^0.4.8",
  • "esdoc": "^0.5.2",
Member

clavecoder commented Jan 20, 2017

  • "@types/node": "^6.0.60",
  • "@types/node": "^7.0.0",
  • "esdoc": "^0.4.8",
  • "esdoc": "^0.5.2",

@clavecoder clavecoder added state_closed and removed state_closed labels Feb 4, 2017

@clavecoder clavecoder changed the title from chore(dependencies): 🌴 Update Dependencies 🔃 🔨 💋 to chore(dependencies): 🌴 Update Dependencies 🚀🔃 💋 Feb 4, 2017

@clavecoder clavecoder changed the title from chore(dependencies): 🌴 Update Dependencies 🚀🔃 💋 to chore(packages): 🌴 Update Dependencies 🚀🔃 💋 Feb 4, 2017

@clavecoder clavecoder requested review from clavecoder and removed request for clavecoder Feb 4, 2017

@clavecoder clavecoder added this to the 0.1 milestone Feb 7, 2017

@clavecoder

This comment has been minimized.

Show comment
Hide comment
@clavecoder

clavecoder Feb 7, 2017

Member

Task for #113

Member

clavecoder commented Feb 7, 2017

Task for #113

@clavecoder clavecoder changed the title from chore(packages): 🌴 Update Dependencies 🚀🔃 💋 to chore(package): 🌴 Update Dependencies 🚀🔃 💋 Feb 7, 2017

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