search

ben-barbier / worldover

0 stars 0 forks source link

An in-range update of karma-coverage-istanbul-reporter is breaking the build 🚨 #25

Open greenkeeper[bot] opened 4 years ago

greenkeeper[bot] commented 4 years ago

The devDependency karma-coverage-istanbul-reporter was updated from 2.1.0 to 2.1.1.

🚨 View failing branch.

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

karma-coverage-istanbul-reporter 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 - ❌ **AnyLint:** They had a total of **23 failures**, **169 warnings**, and **1 notice**. Due to Github limitations, you will only see the first 50 annotations. Use https://anylint.hell.sh for a full report. > Nobody ever won a chess game by resigning. — Savielly Tartakower - ✅ **Travis CI - Branch:** The build **passed**.
Commits

The new version differs by 6 commits.

  • 30ce860 chore(release): 2.1.1
  • e97218c build: upgrade dependencies
  • ee9fb51 fix: add npm funding link
  • 213056c build(deps): bump lodash.template from 4.4.0 to 4.5.0 (#75)
  • 2aefe78 build(deps): bump eslint-utils from 1.3.1 to 1.4.3 (#76)
  • 3eac3fe chore: move to github sponsors

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 2.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.