search

videojs / videojs-contrib-ads

A Tool for Building Video.js Ad Plugins
http://videojs.github.io/videojs-contrib-ads/
Other
381 stars 257 forks source link

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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency karma was updated from 4.0.1 to 4.1.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](https://travis-ci.org/videojs/videojs-contrib-ads/builds/520510456?utm_source=github_status&utm_medium=notification)).
Release Notes for v4.1.0

Bug Fixes

  • client: Enable loading different file types when running in parent mode without iframe (#3289) (7968db6)
  • client: Only create the funky object if message is not a string (#3298) (ce6825f), closes #3296
  • launcher: Log state transitions in debug (#3294) (6556ab4), closes #3290
  • middleware: log invalid filetype (#3292) (7eb48c5), closes #3291
Commits

The new version differs by 6 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)

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:

greenkeeper[bot] commented 5 years ago

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