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 63).
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.
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 63).
9157d41Update docs/changelog.md and set new release id in docs/_config.yml17e735dAdd release documentation for v2.1.090a5d8e2.1.0db6e03bUpdate Changelog.txt and AUTHORS for new releasea3eebd9Build package as part of postversion stepfd79000Fix GitHub asset URL6a7c801Redesign the template (#1339)354c84cMerge pull request #1337 from timcosta/add_called_immediately_before_aftera957ef3update spy names across four tests3aa9919[feature] adds spy.calledImmediatelyBefore and spy.calledImmediatelyAftere401337Merge pull request #1331 from mroderick/remove-next-release-from-docsaf504b9Remove documentation of the 2.x pre-releases8bec6ddRemove @next instructions from documentationfc749faMerge pull request #1333 from eauc/master2058030Add 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.