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

[greenkeeper]

Version 1.2.0 of karma-mocha just got published.

Branch	Build failing 🚨
Dependency	karma-mocha
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.

As karma-mocha 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

Commits

The new version differs by 13 commits .

• 7319c81 chore: release v1.2.0
• 153f363 chore: update contributors
• 7bb69d6 Merge pull request #115 from hackreactor-labs/master
• e4eb5fd feat(reporter): expose mocha test properties
• 7b41f52 feat(reporter): add timestamps to results
• c893d0a fix: "remove mocha stack entries" was too greedy
• 24980f0 Merge pull request #107 from wordofchristian/fix-legacy-ie-compatibility
• 7657b7f Fix: Restore IE 6/7 compatibility
• fc369ff Merge pull request #106 from dpogue/patch-1
• f251fdf chore: Fix failing tests with Karma 1.1.x
• 6a8792e chore: Update mocha to 3.0.0
• 15e03c7 Merge pull request #101 from eiriksm/patch-1
• 3879f4b Update adapter.spec.js

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 🌴

[greenkeeper]

After pinning to 1.1.1 your tests are passing again. Downgrade this dependency 📌.

[gampleman]

Was a temporary failuire.