An in-range update of eslint-plugin-node is breaking the build π¨
greenkeeper opened this issue Β· comments
greenkeeper commented
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/appveyor/branch AppVeyor build failed Details
Release Notes
v5.2.0Bug fixes
- e7878e9 fixed
no-deprecated-api
that has overlookedGLOBAL
androot
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 commented
After pinning to 5.1.1 your tests are passing again. Downgrade this dependency π.