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

[greenkeeper]

Version 4.13.0 of eslint was just published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.12.1
Type	devDependency

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

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 could not complete due to an error Details
• ❌ safetree@gucong Build met error on DaoCloud Details

---

Release Notes

v4.13.0

• 256481b Update: update handling of destructuring in camelcase (fixes #8511) (#9468) (Erin)
• d067ae1 Docs: Don’t use undocumented array-style configuration for max-len (#9690) (Jed Fox)
• 1ad3091 Chore: fix test-suite to work with node master (#9688) (Myles Borins)
• cdb1488 Docs: Adds an example with try/catch. (#9672) (Jaap Taal)

Commits

The new version differs by 6 commits.

• 29c3610 4.13.0
• ac331bc Build: changelog update for 4.13.0
• 256481b Update: update handling of destructuring in camelcase (fixes #8511) (#9468)
• d067ae1 Docs: Don’t use undocumented array-style configuration for max-len (#9690)
• 1ad3091 Chore: fix test-suite to work with node master (#9688)
• cdb1488 Docs: Adds an example with try/catch. (#9672)

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