The version 5.0.0 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 30 commits ahead by 30, behind by 123.
2e455c6Update 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 91.346% when pulling d3354f7bcf8ffd4709326e5c9b199aa87d615e25 on greenkeeper/sinon-5.0.0 into da753512b1223aa7b6c2dcb92703d6c1cef8f9f7 on master.
Coverage remained the same at 91.346% when pulling d3354f7bcf8ffd4709326e5c9b199aa87d615e25 on greenkeeper/sinon-5.0.0 into da753512b1223aa7b6c2dcb92703d6c1cef8f9f7 on master.
Coverage remained the same at 91.346% when pulling d3354f7bcf8ffd4709326e5c9b199aa87d615e25 on greenkeeper/sinon-5.0.0 into da753512b1223aa7b6c2dcb92703d6c1cef8f9f7 on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 5.0.0 of sinon was just published.
The version 5.0.0 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 30 commits ahead by 30, behind by 123.
2e455c6
Update docs/changelog.md and set new release id in docs/_config.yml
7eee963
Add release documentation for v5.0.0
d93cb9d
5.0.0
b9c2c36
Update History.md and AUTHORS for new release
f1f8151
Add postinstall banner pointing to Open Collective
5650f00
Docs: add migration guide for v5
ed3c9dc
Docs: Added example for how to use
restore
a1aced0
Simplify hasFunctionNameSupport
85e3f91
Fix broken test in IE11
6ed81ce
Improve language of fake documentation
67d0bd8
Add yields and yieldsTo to fake
8c1e221
Extract nextTick to own file
5fa0e66
Fix typo in documentation
f14c3cf
Clarify documentation
ea666c0
Fix failing tests in Chromium
There are 30 commits in total.
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: