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 ember-cli-inject-live-reload is breaking the build 🚨 #607

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency ember-cli-inject-live-reload was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

ember-cli-inject-live-reload 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/2774066?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/595393415?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 42 commits.

  • f3e9bea Release 2.0.2
  • 4c4ebc0 Respect liveReloadPort even if same as ember server port (#113)
  • 9581f3b Respect liveReloadPort even if same as ember server port
  • ba3de60 Change entry-point script. (#123)
  • 8b732e0 Change entry-point script.
  • 00616ce Re-roll yarn.lock due to issues with yarn@1.19.0 (#122)
  • f608771 Re-roll yarn.lock due to issues with yarn@1.19.0
  • 5a37c1d [Security] Bump eslint-utils from 1.3.1 to 1.4.2
  • d7fd57f [Security] Bump lodash from 4.17.11 to 4.17.14
  • e9738c0 Bump express from 4.17.0 to 4.17.1
  • f1a66fc Bump express from 4.16.4 to 4.17.0
  • 0367c3f Bump eslint from 5.15.3 to 5.16.0
  • 6800f6d Bump ember-cli-version-checker from 3.1.2 to 3.1.3
  • 3ee4ac7 Bump eslint from 5.15.2 to 5.15.3
  • 3e43143 Bump eslint from 5.15.1 to 5.15.2

There are 42 commits in total.

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 5 years ago

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