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

Question

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

greenkeeper opened this issue 6 years ago · 5 comments

Version 3.0.1 of karma-webpack was just published.

Branch	Build failing 🚨
Dependency	karma-webpack
Current Version	3.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

karma-webpack 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

❌ coverage/coveralls: Coverage pending from Coveralls.io (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes

v3.0.1

2018-09-01

`Bug Fixes`

karma-webpack: allow filename and chunkFilename to be overridden (config.output) (#336) (c256d87)
package: incorrect peerDependency on webpack >= v4.0.0 (peerDependencies) (c1c0ee2)

Commits

The new version differs by 3 commits.

2309401 chore(release): 3.0.1
c1c0ee2 fix(package): incorrect peerDependency on webpack >= v4.0.0 (peerDependencies)
c256d87 fix(karma-webpack): allow filename and chunkFilename to be overridden (config.output) (#336)

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 🌴

Answer 1 · 2018-09-01T05:04:59.000Z

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