An in-range update of karma-qunit is breaking the build 🚨
greenkeeper opened this issue · comments
Version 2.0.2 of karma-qunit was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | karma-qunit |
| Current Version | 2.0.1 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
karma-qunit 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 4 commits.
7bbb633chore: release v2.0.22b91cc6chore: update contributors7d8c138fix(adapter): add timeout before starting qunit8b45e4ftest: add unit test for lib and an integration test
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 🌴
After pinning to 2.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 2.1.0 just got published.
Your tests are still failing with this version. Compare the changes 🚨