An in-range update of karma-coverage is breaking the build 🚨

[greenkeeper]

Version 1.1.2 of karma-coverage was just published.

Branch	Build failing 🚨
Dependency	karma-coverage
Current Version	1.1.1
Type	devDependency

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

karma-coverage 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

v1.1.2

Bug Fixes

• build: Update to lodash 4 (d6d21d2), closes #242
• reporter: replace colons in the output path (3b2bffa)

BREAKING CHANGES

• reporter: the output folder names change, they no longer contain :

Commits

The new version differs by 12 commits.

• 070bba3 chore: release v1.1.2
• 9319dfb chore: update contributors
• 9433b24 Merge pull request #339 from johnjbarton/fix-242
• bf599db Merge pull request #344 from AndrewLane/AndrewLane-patch-1
• 595ab98 Fix exclude typo on the check object
• d6d21d2 fix(build): Update to lodash 4
• 954a555 Merge pull request #345 from johnjbarton/engines
• d4695cf Update travis to match parent karma project
• 54737bf chore: add grunt-cli npm test works out of the box
• 2bc4aa5 docs: add json-summary report type
• 3b2bffa fix(reporter): replace colons in the output path
• 1a876d5 docs: Added none as possible value for type

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]

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