An in-range update of jest-runner-eslint is breaking the build 🚨

[greenkeeper[bot]]

The dependency jest-runner-eslint was updated from 0.7.5 to 0.7.6.

🚨 View failing branch.

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

jest-runner-eslint 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

- ❌ **Test (Node 13):** There are 1 failures, 0 warnings, and 0 notices. - ❌ **Test (Node 12):** null - ❌ **Test (Node 10):** null - ❌ **Test (Node 8):** null - ✅ **Format files:** null

---

Commits

The new version differs by 5 commits.

• d09d788 0.7.6
• 39d96c0 feat: upgrade jest to v25 (#83)
• 8f45e34 Bump handlebars from 4.1.2 to 4.5.3 in /examples/simple (#81)
• fc12d20 Bump handlebars from 4.1.2 to 4.5.3 (#80)
• f14556b chore: docs - correct default value for ‘quiet’ (#79)

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

[greenkeeper[bot]]

• The dependency jest-runner-eslint was updated from 0.7.6 to 0.7.7.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• 1664eef 0.7.7
• 2e20d51 fix: reuse CLIEngine instances (#88)
• a239b61 chore: refresh lockfiles to get rid of security alert (#85)

See the full diff