Closed greenkeeper[bot] closed 5 years ago
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.
devDependency
karma was updated from 3.1.2
to 3.1.3
.Your tests are still failing with this version. Compare changes
devDependency
karma was updated from 3.1.3
to 3.1.4
.Your tests are still failing with this version. Compare changes
The new version differs by 5 commits.
b8b8618
chore: release v3.1.4
10df4ad
chore: update contributors
cc2eff2
fix: restarted browsers not running tests (#3233)
584dddc
fix: improve error msg when bin is a directory (#3231)
bb022a7
fix(file-list): revert "do not preprocess up-to-date files" (#3226) (#3230)
See the full diff
devDependency
karma was updated from 4.0.1
to 4.1.0
.Your tests are passing again with this update. Explicitly upgrade to this version 🚀
The new version differs by 26 commits.
13ed695
chore: release v4.1.0
d844a48
chore: update contributors
ce6825f
fix(client): Only create the funky object if message is not a string (#3298)
7968db6
fix(client): Enable loading different file types when running in parent mode without iframe (#3289)
6556ab4
fix(launcher): Log state transitions in debug (#3294)
7eb48c5
fix(middleware): log invalid filetype (#3292)
c7ebf0b
chore: release v4.0.1
c190c4a
chore: update contributors
375bb5e
fix(filelist): correct logger name. (#3262)
c43f584
fix: remove vulnerable dependency combine-lists (#3273)
4ec4f6f
fix: remove vulnerable dependency expand-braces (#3270)
d5df723
fix(browser): allow updating total specs count (#3264)
c277a6b
fix(launcher): Debug Child Processes exit signal (#3259)
bd95d89
chore: upgrade log4js to v4.0.0 (#3257)
5a47718
chore: release v4.0.0
There are 26 commits in total.
See the full diff
The devDependency karma was updated from
3.1.1
to3.1.2
.🚨 View failing branch.
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](https://travis-ci.org/johngeorgewright/angular-xml/builds/462226832?utm_source=github_status&utm_medium=notification)).Release Notes for v3.1.2
Bug Fixes
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](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: