An in-range update of uglify-js is breaking the build π¨
greenkeeper opened this issue Β· 1 comments
greenkeeper commented
Version 3.0.6 of uglify-js just got published.
Branch | Build failing π¨ |
---|---|
Dependency | uglify-js |
Current Version | 3.0.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As uglify-js is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
v3.0.6
Commits
The new version differs by 6 commits0.
050474a
v3.0.6
f6c805a
print package name alongside version in CLI (#1946)
9464d3c
fix parsing of property access after new line (#1944)
f18abd1
minor fixes to README.md
3be06ad
reorg README for 3.x (#1942)
265008c
improve keyword-related parser errors (#1941)
false
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
jonathanweiss commented
Test result is false negative. Fixed with 2c9c750