An in-range update of optimize-css-assets-webpack-plugin is breaking the build 🚨
greenkeeper opened this issue · comments
The devDependency optimize-css-assets-webpack-plugin was updated from 5.0.1
to 5.0.2
.
This version is covered by your current version range and after updating it in your project the build failed.
optimize-css-assets-webpack-plugin 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).
Commits
The new version differs by 4 commits.
eb7de19
5.0.2
110cc11
Upgrade dependency versions
5cdda05
small formatting improvements to README.md (#96)
64f8309
Handle query string in assetName (#82)
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 🌴
After pinning to 5.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
optimize-css-assets-webpack-plugin was updated from5.0.2
to5.0.3
.
Your tests are still failing with this version. Compare changes