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 151 commits (ahead by 151, 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.0.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 151 commits (ahead by 151, behind by 4).
d5f9ead
v10.0.1
aaaf6f7
Document TAP_DEV_LONGSTACK/SHORTSTACK environs
fbf56f5
ignore 'false' in t.test() args
114635c
Properly filter out tap dir from stack traces
c14ae9f
update readme
884e5c4
v10.0.0
5282f6c
No need to # in the Bail out! message
bfb5942
update tests so that they pass on v0.10
0dfe183
default to buffered tests with jobs>1
939e44e
Actually print #time at the end of the TAP test
884738f
v10.0.0-beta
7be159d
Merge branch 'v10'
73190d6
very forcibly deprecate Test.current()
5061989
package: put the -sfails on npm test command for convenience
f63ea3e
Put back the # time=... directives
There are 151 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.