The version 0.25.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ava.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling 0fa64c65c0dff49f16d7795960b987f048fc9eb4 on greenkeeper/ava-0.25.0 into ec07e24f7854bcd0b970bc6f7bbf52b07dba4184 on master.
Version 0.25.0 of ava was just published.
The version 0.25.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ava.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 15 commits.
a051d3e
0.25.0
4f896c2
Make
t.log()
behave more likeconsole.log()
f00f3c4
Don't set
Error.stackTraceLimit
in worker processesc2b42ec
Mention #1319 as a pitfall
bcb77fc
Recommend skipFiles for VSCode debugging
cd8c91b
Add more clarification for different Babel config in .babelrc.md (#1642)
947f207
Update code-excerpt to ^2.1.1
4a13966
Debug serially in the "Debugging tests with VS Code" recipe (#1634)
aaddc37
Use absolute source map paths in precompiled files
72c53be
support @std/esm (#1618)
29e5dfd
Add TS types for t.snapshot(content, options)
c1faf95
Fix typo in precompiling-with-webpack.md (#1625)
4e8f827
Switch time-require to @ladjs/time-require
965cbc6
Use supertap to generate TAP output (#1610)
4124d77
Update npm, test Node.js 9, detect package-lock churn in CI (#1601)
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: