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

Closed
greenkeeper bot opened this issue May 25, 2018 · 1 comment
Closed

Comments

@greenkeeper
Copy link

greenkeeper bot commented May 25, 2018

Version 3.8.0 of eslint-plugin-promise was just published.

Branch Build failing 🚨
Dependency eslint-plugin-promise
Current Version 3.7.0
Type devDependency

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

eslint-plugin-promise 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 could not complete due to an error Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 9 commits.

  • 67dad97 3.8.0
  • 212e557 docs(changelog): prepare for v3.8.0 (#132)
  • 9b0cbd1 refactor: lookup promise statics from object instead of array (#131)
  • ceb7414 feat: turn off avoid-new in recommended configuration (#119)
  • b5a6423 chore(package): add package-lock.json (#130)
  • 4ebd2c6 fix: ignore event listener callbacks in prefer-await-to-callbacks (#117)
  • 4a3d5b8 fix: ignore top-level awaits in prefer-await-to-then (#126)
  • 0b231da docs: add no-nesting examples (#120)
  • 5956eca docs: add examples to prefer-await-to-then (#121)

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 May 25, 2018

After pinning to 3.7.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

1 participant