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 🚨 #48

Closed
greenkeeper bot opened this issue Dec 12, 2017 · 2 comments
Closed

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

greenkeeper bot opened this issue Dec 12, 2017 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 12, 2017

Version 4.13.1 of eslint was just published.

Branch Build failing 🚨
Dependency eslint
Current Version 4.13.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
  • safetree@gucong DaoCloud builds completed Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v4.13.1
  • b72dc83 Fix: eol-last allow empty-string to always pass (refs #9534) (#9696) (Kevin Partington)
  • d80aa7c Fix: camelcase destructure leading/trailing underscore (fixes #9700) (#9701) (Kevin Partington)
  • d49d9d0 Docs: Add missing period to the README (#9702) (Kevin Partington)
  • 4564fe0 Chore: no-invalid-meta crash if no export assignment (refs #9534) (#9698) (Kevin Partington)
Commits

The new version differs by 6 commits.

  • 234cd26 4.13.1
  • 3b0833f Build: changelog update for 4.13.1
  • b72dc83 Fix: eol-last allow empty-string to always pass (refs #9534) (#9696)
  • d80aa7c Fix: camelcase destructure leading/trailing underscore (fixes #9700) (#9701)
  • d49d9d0 Docs: Add missing period to the README (#9702)
  • 4564fe0 Chore: no-invalid-meta crash if no export assignment (refs #9534) (#9698)

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 Dec 12, 2017

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

@gucong3000
Copy link
Owner

软件截图

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

1 participant