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

[greenkeeper[bot]]

Version 8.0.2 of babel-eslint was just published.

Branch	Build failing 🚨
Dependency	babel-eslint
Current Version	8.0.1
Type	devDependency

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

babel-eslint 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](https://travis-ci.org/DBCDK/tanterne/builds/298201553?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 8 commits ahead by 8, behind by 1.

• a0fbd50 8.0.2
• 2004b91 require correct deps
• fa56d21 Always use unpad (#535)
• 295091d Allow ^ version for babel dependencies (#534)
• d3b8519 fix(package): update babylon to version 7.0.0-beta.31 (#533)
• 54ab4ac 8.0.1
• c1a7882 Update README.md support (#531) [skip ci]
• 51100c9 chore(package): update mocha to version 4.0.0 (#524)

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

[fvsdbc]

Fixed