An in-range update of karma is breaking the build 🚨
greenkeeper opened this issue · comments
The devDependency karma was updated from 3.1.1
to 3.1.2
.
This version is covered by your current version range and after updating it in your project the build failed.
karma 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 could not complete due to an error (Details).
Release Notes for v3.1.2
Bug Fixes
- browser: report errors to console during singleRun=false (#3209) (30ff73b), closes #3131
- changelog: remove release which does not exist (#3214) (4e87902)
- dep: Bump useragent to fix HeadlessChrome version (#3201) (240209f), closes #2762
- deps: upgrade sinon-chai 2.x -> 3.x (#3207) (dc5f5de)
- file-list: do not preprocess up-to-date files (#3196) (5334d1a), closes #2829
- package: bump lodash version (#3203) (d38f344), closes #3177
- server: use flatted for json.stringify (#3220) (fb05fb1), closes #3215
Features
Commits
The new version differs by 11 commits.
7d4d347
chore: release v3.1.2
5077c18
chore: update contributors
fb05fb1
fix(server): use flatted for json.stringify (#3220)
2682bff
feat(docs): callout the key debug strategies. (#3219)
4e87902
fix(changelog): remove release which does not exist (#3214)
30ff73b
fix(browser): report errors to console during singleRun=false (#3209)
5334d1a
fix(file-list): do not preprocess up-to-date files (#3196)
dc5f5de
fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)
d38f344
fix(package): bump lodash version (#3203)
ffb41f9
refactor(browser): log state transitions in debug (#3202)
240209f
fix(dep): Bump useragent to fix HeadlessChrome version (#3201)
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 3.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
karma was updated from3.1.2
to3.1.3
.
Your tests are still failing with this version. Compare changes