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.
Hello lovely humans,
tap just published its new version 7.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 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 224 commits .
05eb736v7.0.0f038a11Don't filter out indented bailouts or version lines from child test procs1c7d987allow SIGKILL in runner timeout tests31f5467split slow runner test up into multiple filese49616dadd the --100 flag for 100% coverage checkccce5a6Remove test that blows up when coverage is engaged14bec9fa test for when a bailout is in a teardownca686f6keep for..in loops from iterating inherited keys4a2011fepipe test: just use js piping instead of fd sharingfbc83b0Handing timeout SIGTERMs after explicit root test end4f50bf0Forcibly kill any child tests on root exit3e4f6daDon't rely on system 'head' exe for EPIPE test14cbf2eDon't nextTick root bailout exit632f935Support use of save file with --bail736e476tap-mocha-reporter v2There are 224 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade