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 should.
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 17 commits .
64ad890Merge branch 'master' of github.com:shouldjs/should.js
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,
should just published its new version 11.2.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 should. 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 17 commits .
64ad890Merge branch 'master' of github.com:shouldjs/should.js48fac91Release 11.2.051a3c5eAdd .only modifier for .keysf1f3d5aMerge pull request #131 from jakearchibald/patch-10fd9c34Minor grammar correctiond2cd6ccRemove very old browsers from testing list77be237Updated build644a407Release 11.1.2813a5f9Merge branch 'master' of github.com:shouldjs/should.js673003eAlways ask for colors0737171Add a bit hacky error to throw instead of full powered AssertionError04d5ce9Update LICENSE3f8c460Update Readme.mdcf1504dMerge pull request #126 from vp2177/masterda9ea39Add .been, i.e. spy.should.have.been.called()There are 17 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.