The version 0.24.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.
Release Notes0.24.0
Highlights đź’ˇ
This is a pretty small release, but a great one if you're solely developing for Node.js 8.3 or above.
You can now use object rest/spread properties in test files without any further Babel configuration. Note that if you're running tests on older versions of Node.js you'll still need to add the relevant Babel plugins, since this new language feature has not yet reached stage 4. 37c9122
Miscellaneous đź•Ż
Before and after hooks are no longer run when all tests are skipped 1cd3a04
Improved output of assertion statements when tests fail 37e8b49
Improved feedback when t.is() values are deeply equal but not the same c41b2af
Updated the Typescript with an example of how to title macros f98a881
We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
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).
Version 0.24.0 of ava was just published.
The version 0.24.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.
Release Notes
0.24.0Highlightsđź’ˇ
This is a pretty small release, but a great one if you're solely developing for Node.js 8.3 or above.
You can now use object rest/spread properties in test files without any further Babel configuration. Note that if you're running tests on older versions of Node.js you'll still need to add the relevant Babel plugins, since this new language feature has not yet reached stage 4. 37c9122
Miscellaneousđź•Ż
t.is()
values are deeply equal but not the same c41b2afAll changesđź“š
v0.23.0...v0.24.0
Thanksđź’Ś
Get involved✌️
We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
Commits
The new version differs by 12 commits.
e401bd1
0.24.0
8141395
Churn and dedupe package-lock
f2979a3
Bump dependencies
efc3b31
Code style tweaks
cb1c3f7
Fix documentation of snapshotDir option
c41b2af
Provide feedback when t.is() values are deeply equal but not the same
1cd3a04
Don't run before and after hooks when all tests are skipped
f98a881
Document how to title macros when using TypeScript
b3c4090
Fix broken link in contributing guide
37c9122
Include syntax-object-rest-spread in default Babel options for Node.js >= 8.3.0
035fd31
Verify package-lock when linting
37e8b49
Use babel-generator to regenerate enhanced assertion statements
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: