An in-range update of eclint is breaking the build 🚨

[greenkeeper[bot]]

Version 2.8.0 of eclint was just published.

Branch	Build failing 🚨
Dependency	eclint
Current Version	2.7.0
Type	devDependency

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

eclint 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 could not complete due to an error [Details](https://travis-ci.org/gucong3000/lint-flow/builds/402514435?utm_source=github_status&utm_medium=notification)

---

Release Notes

v2.8.0

• Drop support for node v4 (#141)
• Update dependencies (#141)
• Add default export (#142)

Commits

The new version differs by 2 commits.

• 08db35f add default export (#142)
• d873675 Update dependencies & drop support for node v4 (#141)

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

[greenkeeper[bot]]

• The devDependency eclint was updated from 2.8.0 to 2.8.1.

Your tests are still failing with this version. Compare changes

Release Notes for v2.8.1

• Fix Chinese Translation (#146)
• Update dependencies (#146)

Commits

The new version differs by 1 commits.

• adbeadd Fix Chinese Translation (#146)

See the full diff