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 623 commits (ahead by 623, behind by 25).
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 85.083% when pulling 2e9bf2abe34fb6109c7e8f1f97c28eedf89cea49 on greenkeeper-sinon-2.0.0 into 81aaa21cb1dc4c25bd184dc7a323351f643f2c5b on master.
Hello lovely humans,
sinon just published its new version 2.0.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 623 commits (ahead by 623, behind by 25).
15a0038
Add dist file to docs
108ac04
Update docs/changelog.md and set new release id in docs/_config.yml
3f5c869
Add release documentation for v2.0.0
02a6ff6
2.0.0
224ec4f
Update Changelog.txt and AUTHORS for new release
c748bc5
Merge pull request #1325 from lucasfcosta/callsFake-docs
fee959d
Merge pull request #1297 from lucasfcosta/getters-setters-new-api
1bda7c4
Merge pull request #1326 from lucasfcosta/remove-unused-chain-behavior
70e96f5
Remove unused chain behavior
bdd3f82
Add docs for the new callsFake behavior
ad58467
Add docs for the new API get and set behaviors
eb7f90f
Add names to previously anonymous getter and setter test functions
e852f4f
Add restore method for stubbed property descriptors
5bbfa51
Allow stubbing getters and setters for function properties
278c2ce
Add getters/setters stub behaviors
There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.