An in-range update of @typescript-eslint/eslint-plugin is breaking the build 🚨

[greenkeeper[bot]]

The dependency @typescript-eslint/eslint-plugin was updated from 2.19.2 to 2.20.0.

🚨 View failing branch.

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

@typescript-eslint/eslint-plugin is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

- ❌ **Travis CI - Branch:** The build **failed**.

---

Release Notes for v2.20.0

2.20.0 (2020-02-17)

Features

• eslint-plugin: [ban-types] allow banning null and undefined (#821) (0b2b887)
• eslint-plugin: [strict-boolean-expressions] refactor, add clearer error messages (#1480) (db4b530)

Commits

The new version differs by 3 commits.

• f9dd7ec chore: publish v2.20.0
• db4b530 feat(eslint-plugin): [strict-boolean-expressions] refactor, add clearer error messages (#1480)
• 0b2b887 feat(eslint-plugin): [ban-types] allow banning null and undefined (#821)

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

After pinning to 2.19.2 your tests are passing again. Downgrade this dependency 📌.

[toddbluhm]

Closing, failure is due to commit message being too long