Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of eslint-plugin-standard is breaking the build 🚨 #29

Open
greenkeeper bot opened this issue Apr 25, 2018 · 1 comment
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Apr 25, 2018

Version 3.1.0 of eslint-plugin-standard was just published.

Branch Build failing 🚨
Dependency eslint-plugin-standard
Current Version 3.0.1
Type devDependency

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

eslint-plugin-standard 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 is in progress Details
  • bitHound - Dependencies 3 failing dependencies. Details
  • bitHound - Code No failing files. Details

Commits

The new version differs by 12 commits.

  • 0174785 3.1.0
  • 6e1aaa6 add npmignore
  • 8be2d27 remove unused .eslintrc
  • e51d5fe remove unmaintained CHANGELOG
  • 6184444 mocha@5
  • 7e6b194 eslint@4
  • 586f36a Merge pull request #26 from delaguilaluis/update-tests
  • 64f91a5 update tests for no-callback-literal
  • f0bc288 Merge pull request #25 from delaguilaluis/allow-undefined-in-errbacks
  • 7ce136a allow undefined in the first position of callbacks
  • a2f6742 Merge pull request #24 from Arcanemagus/rules-docs-url
  • 8072664 Add URL to rule documentation to the metadata

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
Copy link
Author

greenkeeper bot commented Apr 25, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants