An in-range update of @types/chai is breaking the build 🚨

[greenkeeper[bot]]

The devDependency @types/chai was updated from 4.2.0 to 4.2.1.

🚨 View failing branch.

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

@types/chai 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

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build is in progress ([Details](https://travis-ci.org/balassy/aws-lambda-typescript/builds/580497174?utm_source=github_status&utm_medium=notification)). - ❌ **continuous-integration/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/balassy/aws-lambda-typescript/builds/27162575)).

---

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]]

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

[greenkeeper[bot]]

• The devDependency @types/chai was updated from 4.2.1 to 4.2.2.

Your tests are still failing with this version. Compare changes

[greenkeeper[bot]]

• The devDependency @types/chai was updated from 4.2.2 to 4.2.3.

Your tests are still failing with this version. Compare changes

[balassy]

False alarm by AppVeyor.