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

[greenkeeper]

Version 1.4.1 of karma just got published.

Branch	Build failing 🚨
Dependency	karma
Current Version	1.4.0
Type	devDependency

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

As karma is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v1.4.1

Bug Fixes

• runner: Make process kill timeout configurable (ffaa054), closes #2447
• runner: Make process kill timeout configurable - Fix Build (a128e5c), closes #2447
• runner: Test process kill timeout config (99a1d48), closes #2447

Features

• config: allow config to be a default export (9976dce)

Commits

The new version differs by 12 commits .

• acc997a chore: release v1.4.1
• e4833b7 chore: update contributors
• 9ff095e Merge pull request #2541 from vivganes/devdoc
• adf5532 docs(runner): Document processKillTimeout property
• 0bec015 Merge pull request #2533 from vivganes/dev
• b8b02aa Merge pull request #2537 from mattlewis92/switch-gooks-to-husly
• 27d9b12 Merge pull request #2536 from mattlewis92/default-export-config
• 48dad20 chore: switch from ghooks to husky
• 9976dce feat(config): allow config to be a default export
• 99a1d48 fix(runner): Test process kill timeout config
• a128e5c fix(runner): Make process kill timeout configurable - Fix Build
• ffaa054 fix(runner): Make process kill timeout configurable

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴