An in-range update of uglify-js is breaking the build π¨
Closed this issue Β· 3 comments
Version 3.3.1 of uglify-js was just published.
Branch | Build failing π¨ |
---|---|
Dependency | uglify-js |
Current Version | 3.3.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
uglify-js 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
Release Notes
v3.3.1
Commits
The new version differs by 3 commits.
8701a99
v3.3.1
1476c78
add
html-minifier
to benchmarks (#2646)cb6a928
fix infinite loop during
inline
(#2645)
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 3.3.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 3.3.2 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
Release Notes
v3.3.2
Solved.