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-config-mealsup is breaking the build 🚨 #18

Open
greenkeeper bot opened this issue Apr 22, 2019 · 3 comments
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Apr 22, 2019

The devDependency eslint-config-mealsup was updated from 2.6.0 to 2.7.0.

🚨 View failing branch.

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

eslint-config-mealsup 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 for Release 2.7.0
  • Update dependencies and add some new rules (fa0330d)
Commits

The new version differs by 2 commits.

  • 1b1e910 Release v2.7.0
  • fa0330d Update dependencies and add some new rules

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 22, 2019

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

@greenkeeper
Copy link
Author

greenkeeper bot commented Apr 24, 2019

Your tests are still failing with this version. Compare changes

Release Notes for Release 2.7.1
  • Remove rn-raw-text rule (114c789)
Commits

The new version differs by 2 commits.

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Apr 24, 2019

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

See the full diff

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