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

[greenkeeper[bot]]

The devDependency eslint was updated from 6.7.0 to 6.7.1.

🚨 View failing branch.

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

- ❌ **ci-test-win (windows-latest, 12.x):** There are 1 failures, 0 warnings, and 0 notices. - ✅ **ci-test (ubuntu-latest, 12.x):** null - ✅ **lint (12.x):** null - ✅ **ci-test (ubuntu-latest, 10.x):** null - ❌ **ci-test-win (windows-latest, 10.x):** There are 1 failures, 0 warnings, and 0 notices. - ✅ **ci-test (ubuntu-latest, 8.x):** null - ❌ **ci-test-win (windows-latest, 8.x):** There are 1 failures, 0 warnings, and 0 notices.

---

Release Notes for v6.7.1

• dd1e9f4 Fix: revert changes to key-spacing due to regression (#12598) (Kai Cataldo)
• c644b54 Docs: Update README team and sponsors (ESLint Jenkins)

Commits

The new version differs by 4 commits.

• af95154 6.7.1
• 9361824 Build: changelog update for 6.7.1
• dd1e9f4 Fix: revert changes to key-spacing due to regression (#12598)
• c644b54 Docs: Update README team and sponsors

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