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

[greenkeeper]

Version 5.2.0 of eslint-plugin-node just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-node
Current Version	5.1.1
Type	devDependency

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

As eslint-plugin-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
• ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

---

Release Notes

v5.2.0

Bug fixes

• e7878e9 fixed no-deprecated-api that has overlooked GLOBAL and root global variables which are deprecated in Node.js 6.0.0. (#92)

Commits

The new version differs by 5 commits.

• 7189722 5.2.0
• e7878e9 Update: fix missing deprecated APIs in v6 (fixes #92)
• 52ceb11 Chore: rm superfluous argument. (#93)
• 69dc50a Chore: update .travis.yml
• effdd10 Fix: fix tests for linter.reset

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 5.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.