search

kellyselden / package-hint-historic-resolver

Why is CI broken?
http://package-hint-historic-resolver.herokuapp.com/
8 stars 2 forks source link

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

Open greenkeeper[bot] opened 4 years ago

greenkeeper[bot] commented 4 years ago

The devDependency babel-eslint was updated from 10.0.3 to 10.1.0.

🚨 View failing branch.

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

babel-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 - ❌ **percy/package-hint-historic-resolver:** Visual changes processing ([Details](https://percy.io/kellyselden/package-hint-historic-resolver/builds/4327663?utm_campaign=kellyselden&utm_content=package-hint-historic-resolver&utm_source=github_status_private)). - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/kellyselden/package-hint-historic-resolver/builds/656051726?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 2 commits.

  • 4bd049e 10.1.0
  • 2c754a8 Update Babel to ^7.7.0 and enable Flow enums parsing (#812)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

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