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 nodeunit.
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.
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 93.916% when pulling 529c17dbe2c861e994b42917b5dd94a87a5f1b92 on greenkeeper-nodeunit-0.11.0 into 1ad0e2ddb877d373f6af31dde0be8041d3fde00a on master.
Coverage remained the same at 93.916% when pulling 4e67aecc310093d217d63b1d872b8be11533edb0 on greenkeeper-nodeunit-0.11.0 into 4d81c5f4314cbcb9a09430fb4c208326b5349f29 on master.
Hello lovely humans,
nodeunit just published its new version 0.11.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 nodeunit. 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 22 commits .
be1bde2
0.11.0
6ad4160
Merge pull request #337 from zhuangya/upgrade-tap
7ebc211
chore: upgrade tap to 10.0.2
b54bafe
Update CONTRIBUTORS.md
f3d3df2
Merge pull request #331 from ben-pushspring/master
efaa4b4
Merge pull request #329 from brettz9/allow-no-options
dc7e3c7
Explicitly exit out of nodeunit in both success and failure cases
f708bef
Allow invoking browser
run()
without optionsd5806bb
Merge pull request #327 from scottgonzalez/patch-1
513d140
Fix typo
468b759
Merge pull request #60 from broofa/master
f8e93e4
replaced embedded copy of ejs with more up-to-date version in npm
cf20dae
removed old console.log stub
4ff6c67
removed node_modules from git
6b02814
added travis ci status badge to readme
There are 22 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.