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

[Greenkeeper]

The devDependency @typescript-eslint/eslint-plugin was updated from 1.5.0 to 1.6.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 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 failed (Details).

---

Commits

The new version differs by 12 commits.

• ab3c1a1 chore: publish v1.6.0
• a4f95d3 feat(*): change TypeScript version range to >=3.2.1 <3.5.0 (#399)
• 95a948d chore: initial pull request templates
• 5d81f8c docs(eslint-plugin): fix markdown format (#394)
• 492b737 fix(parser): Make eslint traverse enum id (#383)
• f29d1c9 fix(eslint-plugin): Fix allowExpressions false positives in explicit-function-return-type and incorrect documentation (#388)
• cebcfe6 fix(eslint-plugin): no-type-alias: fix typeof alias erroring (#380)
• bf04398 fix(typescript-estree): add ExportDefaultDeclaration to union DeclarationStatement (#378)
• 643a223 fix(eslint-plugin): explicit-function-return-type: ensure class arrow methods are validated (#377)
• 6f5c0fa docs(eslint-plugin): list rules requiring type info (#360)
• ad0f2be fix(eslint-plugin): member-naming false flagging constructors (#376)
• bea6b92 feat(eslint-plugin): allow explicit variable type with arrow functions (#260)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[Greenkeeper]

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