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 186 commits (ahead by 186, 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.3.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 186 commits (ahead by 186, behind by 4).
a9c4b62
v10.3.0
65a425f
Add -o --output-file option to store raw TAP
c9f4671
-J is a flag, not an option
028eee2
Don't put unfiltered stack traces in output tests
1e1cf7d
don't require('tap') in test files
53f9571
drop 5 and 0.12 on appveyor, add 6
318838f
more useful yaml messaging in test/test.js
a75fe1a
v10.2.2
7a45171
Fix teardown/startup timing issues
67b03a9
add test case demonstrating odd teardown timing
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
There are 186 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.