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 is breaking the build 🚨 #231

Open
greenkeeper bot opened this issue Jun 26, 2018 · 1 comment
Open

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

greenkeeper bot opened this issue Jun 26, 2018 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jun 26, 2018

Version 5.0.1 of eslint was just published.

Branch Build failing 🚨
Dependency [eslint](https://github.com/eslint/eslint)
Current Version 5.0.0
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 failed Details

Release Notes v5.0.1
  • 196c102 Fix: valid-jsdoc should allow optional returns for async (fixes #10386) (#10480) (Mark Banner)
  • 4c823bd Docs: Fix max-lines-per-function correct code's max value (#10513) (Rhys Bower)
Commits

The new version differs by 4 commits.

  • caeb223 5.0.1
  • 125dc34 Build: changelog update for 5.0.1
  • 196c102 Fix: valid-jsdoc should allow optional returns for async (fixes #10386) (#10480)
  • 4c823bd Docs: Fix max-lines-per-function correct code's max value (#10513)

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
Contributor Author

greenkeeper bot commented Jun 26, 2018

After pinning to 5.0.0 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