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 tap.
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 176 commits (ahead by 176, behind by 4).
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,
tap just published its new version 10.2.1.
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 tap. 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 176 commits (ahead by 176, behind by 4).
0e16fae
v10.2.1
df9f371
don't use arrow functions in tests
72a3a9a
don't test on node 5
0c63268
v10.2.0
2aa0f21
Respond to TAP_DEBUG and NODE_DEBUG environs
7bd7f22
Catch errors thrown in teardown handlers
7b96e86
Improve root-level thrown error reporting
9cba659
don't let an occupied test slip past endAll
29156e4
Handle unhandledRejection as a root TAP error
f9fa211
better inspect data
4019cb1
If results are synthetically set, don't clobber when parser ends
fb31f2a
monkeypatch exit as well as reallyExit
bf6f51e
v10.1.2
bdb1d80
Inherit bailout results from parent test
0aa4202
Support old nodes that did not respect process.exitCode
There are 176 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.