hisptz/action-tracker

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

greenkeeper opened this issue · 2 comments

greenkeeper commented

The devDependency karma was updated from 4.1.0 to 4.2.0.

🚨 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 failed (Details).
  • ❌ Travis CI - Branch: The build failed.
Release Notes for v4.2.0

Bug Fixes

  • logging: Util inspect for logging the config. (#3332) (70b72a9)
  • reporter: format stack with 1-based column (#3325) (182c04d), closes #3324
  • server: Add error handler for webserver socket. (#3300) (fe9a1dd)
Commits

The new version differs by 13 commits.

  • 42933c9 chore: release v4.2.0
  • db1ea57 chore: update contributors
  • a1049c6 chore: update eslint packages to latest and fix complaints (#3312)
  • 70b72a9 fix(logging): Util inspect for logging the config. (#3332)
  • 1087926 fix typo: (#3334)
  • 182c04d fix(reporter): format stack with 1-based column (#3325)
  • f0c4677 docs(travis): Correct the docs to also show how to do it on Xenial (#3316)
  • 3aea7ec chore(deps): update core-js -> ^3.1.3 (#3321)
  • 5e11340 chore: revert back to Mocha 4 (#3313)
  • 1205bce chore(test): fix flaky test cases (#3314)
  • 7f40349 Cleanup dependencies (#3309)
  • 7828bea chore: update braces and chokidar to latest versions (#3307)
  • fe9a1dd fix(server): Add error handler for webserver socket. (#3300)

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 commented

After pinning to 4.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper commented
  • The devDependency karma was updated from 4.2.0 to 4.3.0.

Your tests are still failing with this version. Compare changes

Release Notes for v4.3.0

Bug Fixes

Features

Commits

The new version differs by 13 commits.

  • fa6be15 chore: release v4.3.0
  • 0ed9eba chore: update contributors
  • 5f13e11 fix(server): Simplify 'dom' inclusion. (#3356)
  • 817fbbd feat(config): socket.io server pingTimeout config option. (#3355)
  • c5f3560 feat(preprocessor): preprocessor_priority execution order. (#3303)
  • 6c5add2 fix(build): switch from yarn to package-lock.json (#3351)
  • 1c6c690 fix(travis): Pin to trusty (#3347)
  • 62d4c5a feat(runner):
  • 582a406 fix(config): Simpilfy error proceesing. (#3345)
  • 1489e9a fix(test): test:client silently failing on Travis (#3343)
  • 094bcc6 chore(deps): npm install karma-browserstack-launcher (#3344)
  • 5614c04 fix(deps): lodash update. (#3341)
  • 177e2ef feat(async): frameworks can be loaded asynchronously (#3297)

See the full diff