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 ava.
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.
Coverage remained the same at 95.652% when pulling 3621f1e5a5469b32be7e32b07bfcf1bf2b2e5a6b on greenkeeper-ava-0.17.0 into 7a34cddcbb48eb18e94ac4b2fb36dbb4898cc1a6 on master.
Coverage remained the same at 95.652% when pulling 3621f1e5a5469b32be7e32b07bfcf1bf2b2e5a6b on greenkeeper-ava-0.17.0 into 7a34cddcbb48eb18e94ac4b2fb36dbb4898cc1a6 on master.
Coverage remained the same at 95.652% when pulling 3621f1e5a5469b32be7e32b07bfcf1bf2b2e5a6b on greenkeeper-ava-0.17.0 into 7a34cddcbb48eb18e94ac4b2fb36dbb4898cc1a6 on master.
Coverage remained the same at 95.652% when pulling 422e986b937aca477d83be0410a563dac8b37207 on greenkeeper-ava-0.17.0 into ad39c67d58c0f6f25924be9295d11d8ecb180b44 on master.
Coverage remained the same at 95.652% when pulling 422e986b937aca477d83be0410a563dac8b37207 on greenkeeper-ava-0.17.0 into ad39c67d58c0f6f25924be9295d11d8ecb180b44 on master.
Coverage remained the same at 95.652% when pulling 422e986b937aca477d83be0410a563dac8b37207 on greenkeeper-ava-0.17.0 into ad39c67d58c0f6f25924be9295d11d8ecb180b44 on master.
Hello lovely humans,
ava just published its new version 0.17.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 ava. 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 51 commits .
b24495d
0.17.0
056f227
bump dev dependencies and make XO happy
26bcab0
temp fix for Node.js internal stack traces showing
2d04763
Add docs for test parameter need to be named
t
(#1096)59254b7
Use current working directory if no
package.json
(#1044)3c3a6d8
add XO badge
e0a170b
Speed up CI (#1076)
257b34d
Upgrade XO (#1080)
3ea2ba1
Ensure test files load correct AVA installation (#1085)
476c653
Change the current working directory of tests to be the same directory as package.json (#1074)
1b214be
clean up caching precompiler (#1077)
6165a23
linting: turn off the
no-use-extend-native
rulee10338e
Update readme.md (#1075)
dae3a44
make XO happy
c258d03
Fix link to configuration in readme (#1073)
There are 51 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade