-
-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of karma-webpack is breaking the build 🚨 #364
Comments
After pinning to 3.0.0 your tests are passing again. Downgrade this dependency 📌. |
Version 3.0.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
I guess that's a false-negative. Let's check |
Version 3.0.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 3.0.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Version 3.0.1 of karma-webpack was just published.
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
Release Notes
v3.0.12018-09-01
Bug Fixes
filename
andchunkFilename
to be overridden (config.output
) (#336) (c256d87)peerDependency
onwebpack >= v4.0.0
(peerDependencies
) (c1c0ee2)Commits
The new version differs by 3 commits.
2309401
chore(release): 3.0.1
c1c0ee2
fix(package): incorrect
peerDependency
onwebpack >= v4.0.0
(peerDependencies
)c256d87
fix(karma-webpack): allow
filename
andchunkFilename
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 🌴
The text was updated successfully, but these errors were encountered: