The version 0.21.0 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.
Release Notes0.21.0
This is primarily a bug fix release, but some features did sneak in:
Additional arguments can be passed when profiling 05bfafe
Though not officially supported, AVA now works better with Wallaby.js’ diff view 3f6e134
Expanded the Webstorm recipe to include setup instructions using npm2b4e35d
This release includes the following patches:
Fixes for t.deepEqual() and magic assert diffs 9e4ee3f
Ensure AVA doesn’t use Buffer APIs that are unavailable in Node.js releases older than 4.5 d0fc8c9
Changed Flow typing of the t.throws() promise return value to be any4a769f8
Update Flow typing of test() so macros are compatible with the latest flow-bine794e73
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.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 92.727% when pulling 6abcf75dce42736e09d4b621b3549a083626dca4 on greenkeeper/ava-0.21.0 into a614cede18fb70e45e95997c0da4f94e96140e60 on master.
Coverage remained the same at 92.727% when pulling 6abcf75dce42736e09d4b621b3549a083626dca4 on greenkeeper/ava-0.21.0 into a614cede18fb70e45e95997c0da4f94e96140e60 on master.
Version 0.21.0 of ava just got published.
The version 0.21.0 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.
Release Notes
0.21.0This is primarily a bug fix release, but some features did sneak in:
npm
2b4e35dThis release includes the following patches:
t.deepEqual()
and magic assert diffs 9e4ee3fBuffer
APIs that are unavailable in Node.js releases older than 4.5 d0fc8c9t.throws()
promise return value to beany
4a769f8test()
so macros are compatible with the latestflow-bin
e794e73Thanks
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 17 commits.
a1afbe3
0.21.0
f9b865a
Update safe-buffer in package-lock.json
d0fc8c9
Avoid directly using newish Buffer APIs (#1448)
9e4ee3f
Upgrade concordance (#1450)
761f7f7
Update expected package.json version in readme (#1449)
e794e73
Resolve strict checking of function call arity (#1441)
1cbcb06
Revert "Handle package-lock.json churn"
8d981bf
Handle package-lock.json churn
c09462c
Assume npm 5.2.0 during development and CI
2b4e35d
Add an additional npm-based recipe for Jetbrains IDEs (#1444)
4a769f8
Update flow def for AssertContext.throws to match typescript def (#1443)
3f6e134
Include raw actual and expected objects in AssertionError (#1432)
0069a7e
Remove non-existent npm run script in maintaining.md (#1434)
e58e96e
Minor readme tweak (#1422)
5ae434a
Bump dependencies
There are 17 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: