An in-range update of karma-jasmine-html-reporter is breaking the build 🚨

[greenkeeper[bot]]

The devDependency karma-jasmine-html-reporter was updated from 1.4.0 to 1.4.1.

🚨 View failing branch.

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

karma-jasmine-html-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

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/leonardochaia/timoneer/builds/524164393?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 2 commits.

• 83f51f0 Bump to 1.4.1
• 828a932 fix: set specFilter only when needed (#24)

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]]

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

[greenkeeper[bot]]

• The devDependency karma-jasmine-html-reporter was updated from 1.4.1 to 1.4.2.

Your tests are still failing with this version. Compare changes

Release Notes for v1.4.2

Only override specFilter if query exists

Commits

The new version differs by 2 commits.

• dfe32de Bump to 1.4.2
• 453f6b4 fix: always override specFilter if query exists (#25)

See the full diff