The version 0.22.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.22.0
There's but a few commits in this release, but we've made a big change to how AVA manages its test workers 👩🏼🔬👨🏼🏭👨🏿🚀👨🏻⚕️👩🏽💼.
Highlights
Default concurrency
We now cap the number of concurrent workers to the number of CPU cores on your machine. Previously AVA started workers for each test file, so if you had many test files this could actually bring things to a halt. 465fcec
You can still customize the concurrency by setting the concurrency option in AVA's package.json configuration, or by passing the --concurrency flag. We've also beefed up input validation on that flag. b6eef5a
Unfortunately this does change how test.only() behaves. AVA can no longer guarantee that normal tests won't run. For now, if you want to use test.only(), you should run tests from just that file. We have an open issue to add an --only flag, which will ensure that AVA runs just the test.only() tests. If you'd like to help us with that please head on over to #1472.
t.log()
We've also added t.log(), which lets you print a log message contextually alongside the test result, instead of immediately printing it to stdout like console.log. 14f7095
Miscellaneous
The WebStorm recipe has been updated with instructions on how to enable the Node.js inspector. d8c21a6
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).
Version 0.22.0 of ava just got published.
The version 0.22.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.22.0There's but a few commits in this release, but we've made a big change to how AVA manages its test workers 👩🏼🔬👨🏼🏭👨🏿🚀👨🏻⚕️👩🏽💼.
Highlights
Default concurrency
We now cap the number of concurrent workers to the number of CPU cores on your machine. Previously AVA started workers for each test file, so if you had many test files this could actually bring things to a halt. 465fcec
You can still customize the concurrency by setting the
concurrencyoption in AVA'spackage.jsonconfiguration, or by passing the--concurrencyflag. We've also beefed up input validation on that flag. b6eef5aUnfortunately this does change how
test.only()behaves. AVA can no longer guarantee that normal tests won't run. For now, if you want to usetest.only(), you should run tests from just that file. We have an open issue to add an--onlyflag, which will ensure that AVA runs just thetest.only()tests. If you'd like to help us with that please head on over to #1472.t.log()We've also added
t.log(), which lets you print a log message contextually alongside the test result, instead of immediately printing it tostdoutlikeconsole.log. 14f7095Miscellaneous
t.notThrows()example has been clarified 57f5007All changes
v0.21.0...v0.22.0Thanks
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 10 commits.
dd9e8b20.22.0b6eef5aFail hard when--concurrencyis set to invalid values (#1478)57f5007Fix typo int.notThrowsexample (#1486)d8c21a6Update debugging with webstorm recipe (#1483)14f7095Implement t.log() (#1452)e28be05Fixed makeApp() in endpoint testing recipe (#1479)465fcecLimit concurrency to the number of CPU cores (#1467)4eea226Use --verbose when testing CLI output (#1477)a0d5b37Simplify readme avatar URLs31b1380Add tests for improper-usage-messages (#1462)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: