This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of sinon.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 641 commits (ahead by 641, behind by 50).
9157d41Update docs/changelog.md and set new release id in docs/_config.yml
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 94.737% when pulling cc96f450575d267b5489c67825a9084821d7658b on greenkeeper-sinon-2.1.0 into 446321fcd29f296f06dad1cabd850e1d4a7e12b2 on master.
Hello lovely humans,
sinon just published its new version 2.1.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of sinon. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 641 commits (ahead by 641, behind by 50).
9157d41
Update docs/changelog.md and set new release id in docs/_config.yml
17e735d
Add release documentation for v2.1.0
90a5d8e
2.1.0
db6e03b
Update Changelog.txt and AUTHORS for new release
a3eebd9
Build package as part of postversion step
fd79000
Fix GitHub asset URL
6a7c801
Redesign the template (#1339)
354c84c
Merge pull request #1337 from timcosta/add_called_immediately_before_after
a957ef3
update spy names across four tests
3aa9919
[feature] adds spy.calledImmediatelyBefore and spy.calledImmediatelyAfter
e401337
Merge pull request #1331 from mroderick/remove-next-release-from-docs
af504b9
Remove documentation of the 2.x pre-releases
8bec6dd
Remove @next instructions from documentation
fc749fa
Merge pull request #1333 from eauc/master
2058030
Add missing space from deprecated message (#1334)
There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.