The version 4.1.1 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of sinon.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 5 commits.
3a0e28bUpdate docs/changelog.md and set new release id in docs/_config.yml
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling f017341957b8c0649e3edc1559c4e601528b87c4 on greenkeeper/sinon-4.1.1 into fe31dd8d70359b92a62d3e6063e46cbe32657b38 on master.
Coverage remained the same at 100.0% when pulling f017341957b8c0649e3edc1559c4e601528b87c4 on greenkeeper/sinon-4.1.1 into fe31dd8d70359b92a62d3e6063e46cbe32657b38 on master.
Coverage remained the same at 100.0% when pulling f017341957b8c0649e3edc1559c4e601528b87c4 on greenkeeper/sinon-4.1.1 into fe31dd8d70359b92a62d3e6063e46cbe32657b38 on master.
Version 4.1.1 of sinon was just published.
The version 4.1.1 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of sinon.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 5 commits.
3a0e28b
Update docs/changelog.md and set new release id in docs/_config.yml
989e15b
Add release documentation for v4.1.1
df3adf0
4.1.1
0e9bf90
Update History.md and AUTHORS for new release
9d9c372
Remove "engines" from package.json
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: