ChocPanda / mambda

A Middleware and lifecycle framework for build AWS Lambdas
MIT License
5 stars 1 forks source link

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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency ava was updated from 2.1.0 to 2.2.0.

🚨 View failing branch.

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 - ❌ **ci/circleci: setup:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/ChocPanda/mambda/558?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

Release Notes for 2.2.0

Enhancements

You can now specify an alternative config file, using the --config CLI argument. This is useful if you want to run unit tests separately from integration tests, since you can have a config file specific to your integration tests which specifies different glob patterns. 2dae2bf

Bug fixes

We're now faking the new hasColors() method for better compatibility with Node.js 12. d399797

Node.js 11

We've removed Node.js 11 from our test matrix. You should upgrade to Node.js 12. 90acbb9

All changes

v2.1.0...v2.2.0

Thanks

Thank you @langri-sha, @keyspress, @cdaringe and @okyantoro. We couldn't have done this without you!

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 9 commits.

  • 2451484 2.2.0
  • e528ad2 Bump dependencies
  • 2dae2bf Implement --config flag
  • 58b2350 Disable deprecation warnings in reporter tests
  • d399797 Fake hasColors() in worker processes
  • 90acbb9 Stop testing Node.js 11, remove from engines entry
  • 533ee4b Link to VSCode debugging recipe
  • dc91725 Fix grammar in readme
  • 851316f Remove Flow references

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 5 years ago

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

ChocPanda commented 5 years ago

Fixed by #31