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

[greenkeeper[bot]]

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency @typescript-eslint/parser was updated from 2.25.0 to 2.26.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/parser 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 **errored**.

---

Release Notes for v2.26.0

2.26.0 (2020-03-30)

Bug Fixes

• eslint-plugin: [no-explicit-any] error with ignoreRestArgs (#1796) (638d84d)
• eslint-plugin: [no-unsafe-call] allow import expressions (#1800) (4fa7107)
• eslint-plugin: [no-unsafe-return] error with <TS3.7 (#1815) (f3160b4)

Features

• eslint-plugin-tslint: support tslint 6 (#1809) (7d963fd)
• typescript-estree: add option to ignore certain folders from glob resolution (#1802) (1e29e69)

Commits

The new version differs by 10 commits.

• 151f89b chore: publish v2.26.0
• 543bc79 docs(eslint-plugin): add missing invalid-void link to ROADMAP.md (#1816)
• bfdffb4 chore: separate linting checks to their own step (#1801)
• f3160b4 fix(eslint-plugin): [no-unsafe-return] error with <TS3.7 (#1815)
• 1e29e69 feat(typescript-estree): add option to ignore certain folders from glob resolution (#1802)
• 7d963fd feat(eslint-plugin-tslint): support tslint 6 (#1809)
• 638d84d fix(eslint-plugin): [no-explicit-any] error with ignoreRestArgs (#1796)
• 4fa7107 fix(eslint-plugin): [no-unsafe-call] allow import expressions (#1800)
• b1b8284 docs(eslint-plugin): [prefer-readonly-parameter-types] fix invalid example (#1791)
• 258fdd0 docs: title wording in root readme (#1787)

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.25.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.