An in-range update of webpack-merge is breaking the build π¨
greenkeeper opened this issue Β· 2 comments
Version 4.1.4 of webpack-merge was just published.
Branch | Build failing π¨ |
---|---|
Dependency | webpack-merge |
Current Version | 4.1.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
webpack-merge 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).
Commits
The new version differs by 6 commits.
91c9ab5
4.1.4
2717034
Update lib
34e7546
chore(docs): Add changelog for 4.1.4
073c16f
chore: Add @DanielRuf to contributors
d67d9c7
Merge pull request #102 from DanielRuf/chore/remove-bithound
a60a920
chore: remove bitHound
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 4.1.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
webpack-merge was updated from4.1.4
to4.1.5
.
Your tests are passing again with this update. Explicitly upgrade to this version π
Commits
The new version differs by 7 commits.
2c98a8d
4.1.5
a4b75fe
Update lib
ea4d003
chore: Add @adrienharnay to contributors
d05e2d6
Merge pull request #108 from adrienharnay/patch-1
e2d85c2
Update README to comply to new Webpack API
ef6dfb3
Merge pull request #105 from escapedcat/patch-1
661ecb2
chore(docs): add build info #104
See the full diff