An in-range update of ava is breaking the build 🚨

greenkeeper[bot] commented 4 years ago

The devDependency ava was updated from `3.1.0` to `3.2.0`.

This version is covered by your current version range and after updating it in your project the build failed.

ava is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **Travis CI - Branch:**

The build **failed**.

Release Notes for 3.2.0

This release improves the integration with the new @ava/typescript package, which allows AVA to load pre-compiled TypeScript files.

First, install the new @ava/typescript package:

npm install --save-dev @ava/typescript@^1.1

Now let's assume your TypeScript files are in a src directory, output to a build directory. Configure AVA like so:

ava.config.js file:

export default {
  typescript: {
    rewritePaths: {
      'src/': 'build/'
    }
  }
}

Compile your TypeScript files and run your tests! Or, to run a specific test file, run npx ava src/test.ts.

For more examples see the @ava/typescript package.

As exciting as this is, it's still early days. We need your help improving our TypeScript support. Check out the open issues.

Other changes

See v3.1.0...v3.2.0 for all changes.

Commits

The new version differs by 4 commits.

ea05758 3.2.0
6c91153 Improve integration with the TypeScript provider
7ccb208 Clarify comment
f4008d5 Map provider protocols to 'levels'

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:

greenkeeper[bot] commented 4 years ago

After pinning to 3.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 4 years ago

The devDependency ava was updated from 3.2.0 to 3.3.0.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 3.3.0

AVA can now load ESM test files! 🎉Thank you @arlac77 for making this happen. Check our updated ES Modules recipe for details.

Our ESM support is still incomplete. Progress is tracked in the ESM support project. Join us, won't you?

Other changes

See v3.2.0...v3.3.0 for all changes.

Commits

The new version differs by 3 commits.

c166e05 3.3.0
362b6f9 Upgrade @ava/babel
04ba44b Support loading ESM test files

See the full diff

greenkeeper[bot] commented 4 years ago

The devDependency ava was updated from 3.3.0 to 3.4.0.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 3.4.0

Introducing the `t.try()` assertion

The new t.try() allows you to try assertions without causing the test to fail:

test('do the thing', async t => {
  const attempt = () => t.try(tt => {
    const result = await getResult()
    // getResult() can be flaky and sometimes throws :(
    tt.is(result, 'expected')
  })

  const firstAttempt = await attempt()
  if (firstAttempt.passed) return firstAttempt.commit()

  t.log('Retrying (just once)')
  firstAttempt.discard()
  const secondAttempt = await attempt()
  secondAttempt.commit()
})

You can use any test implementation with t.try(), including (arrays of) macros. You can decide what to do with attempts. You can even run attempts concurrently, so long as they don't use snapshot assertions.

This is great building block for handling all kinds of advanced test scenarios. We can't wait to see what you'll do with it! Find out more in the assertion documentation.

This feature was previously behind an experimental flag. That flag has now been removed. If you have enabled the flag you'll have to update your AVA config. Also note that as of this release, attempt titles are always prefixed with the title of the parent test 7ee3a0e.

Once again, thank you @qlonik for contributing this new assertion.

Other changes

The t.throws() and t.throwsAsync() assertions can now be called with undefined as the second argument. Previously, if you wanted to set an assertion message but did not want to provide any expectations for the thrown error you had to pass null. That's still allowed, of course. d0e2161 @stavalfi
ava.config.js files once again work with our @ava/typescript package f4d4edd
Our TypeScript definition no longer references @types/node 7a1dacf
We've improved the error message shown when test.cb() is used with asynchronous functions or observables f5a8c2b @toddkcarlson
The Vue recipe has been updated to use jsdom-global instead of browser-env 3f9c616 @Scrum
@fisker optimized how we detect ESM support 8831f54

See v3.3.0...v3.4.0 for all changes.

Commits

The new version differs by 16 commits.

8630636 3.4.0
12ba7bc Ship t.try() without requiring opt-in
f4d4edd Evaluate ava.config.js scripts in current context
8831f54 Improve detection of ESM support
d0e2161 Support undefined as second argument to t.throws and t.throwsAsync
324e45f Document t.try() (#2251)
da52e5f Bump dependencies
55a3649 Ensure t.try() assigns unique titles when multiple implementations are passed
7ee3a0e Prefix attempt titles with that of parent test
a69e4f2 Bump dependencies
7a1dacf Remove @types/node reference
3f9c616 Update Vue recipe to use JSDom rather than browser-env
f5a8c2b Improve error message when test.cb() is used with promises
c166e05 3.3.0
362b6f9 Upgrade @ava/babel

There are 16 commits in total.

See the full diff

jwandrews / has-task-runner