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

[greenkeeper]

Version 1.1.1 of karma-jasmine was just published.

Branch	Build failing 🚨
Dependency	karma-jasmine
Current Version	1.1.0
Type	devDependency

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

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

---

Commits

The new version differs by 10 commits.

• f48a731 chore: release v1.1.1
• 00b97de chore: update contributors
• 4c3221a Merge pull request #187 from maksimr/patch-fix-travis-npm
• 4411737 Merge pull request #140 from tehvgg/master
• 23ef6b3 chore: fix problem with npm on travis for old nodejs
• 372adb9 Merge pull request #162 from TheModMaker/feat-afterAllErrors
• f3fa264 feat: Propagate errors thrown in afterAll blocks
• 9879a94 Revert "Allow lib adapter through so it can be used when pointing to this repo as a dev dependency."
• 6ae78a1 Allow lib adapter through so it can be used when pointing to this repo as a dev dependency.
• 7373f2e Check that a message is a string before calling .indexOf() when building the relevant stack.

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