The version 4.1.3 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 12 commits.
39b0849Update 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 21f2fb810c9cf88060a07e8de90278d280ded8b2 on greenkeeper/sinon-4.1.3 into 2c46e9b974b813ed893957dea8b8a6e5e971ed09 on master.
Coverage remained the same at 100.0% when pulling 21f2fb810c9cf88060a07e8de90278d280ded8b2 on greenkeeper/sinon-4.1.3 into 2c46e9b974b813ed893957dea8b8a6e5e971ed09 on master.
Coverage remained the same at 100.0% when pulling 21f2fb810c9cf88060a07e8de90278d280ded8b2 on greenkeeper/sinon-4.1.3 into 2c46e9b974b813ed893957dea8b8a6e5e971ed09 on master.
Version 4.1.3 of sinon was just published.
The version 4.1.3 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 12 commits.
39b0849
Update docs/changelog.md and set new release id in docs/_config.yml
6f9af25
4.1.3
c6bd1de
Update History.md and AUTHORS for new release
911c498
Spy passes through calling with
new
(#1626)271d84a
Update external_howtos.yml
e96ff8c
CircleCI Integration (#1479)
88e9132
Upgrade type-detect dependency to 4.0.5
45c4d57
Move yieldsAsync* documentation to the first yieldsAsync*
8c54024
Remove sinon.restore(object|method) from v3.x+ docs
9ae6f73
Remove sinon.log from 2.x+ docs
0111ed0
Update markdownlinter-cli to official v0.4.0
109e7b7
Add markdownlint to dependencies
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: