-
-
Notifications
You must be signed in to change notification settings - Fork 87
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 uglify-js is breaking the build 🚨 #115
Comments
After pinning to 3.6.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes Release Notes for v3.6.2
CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.6.3
CommitsThe new version differs by 18 commits.
There are 18 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.6.4
CommitsThe new version differs by 11 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.6.5
CommitsThe new version differs by 15 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.6.6
CommitsThe new version differs by 11 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.6.7
|
Your tests are still failing with this version. Compare changes Release Notes for v3.6.8
|
Your tests are still failing with this version. Compare changes Release Notes for v3.6.9
CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.7.0
CommitsThe new version differs by 15 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.7.1
CommitsThe new version differs by 14 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.7.2
CommitsThe new version differs by 10 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.7.3
CommitsThe new version differs by 8 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.7.5
CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.7.6
|
Your tests are still failing with this version. Compare changes Release Notes for v3.7.7
CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.8.0
CommitsThe new version differs by 23 commits.
There are 23 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.8.1
CommitsThe new version differs by 14 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.9.0
CommitsThe new version differs by 31 commits.
There are 31 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.9.1
CommitsThe new version differs by 34 commits.
There are 34 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.9.2
CommitsThe new version differs by 74 commits.
There are 74 commits in total. See the full diff |
The devDependency uglify-js was updated from
3.6.0
to3.6.1
.🚨 View failing branch.
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
Release Notes for v3.6.1
Commits
The new version differs by 10 commits.
a82003d
v3.6.1
da9f162
report errors correctly in ufuzz (#3456)
8a4c707
account for
catch
in constant lambda expressions (#3454)0a63f2f
workaround V8 RegExp bug (#3453)
931ac66
fix corner case in
hoist_props
(#3452)35338a1
handle function/variable name collisions correctly (#3451)
d57b606
exclude mangling of addEventListener parameters (#3445)
00ada04
facilitate Webpack compatibility (#3435)
a31c477
fix variable scope determination (#3449)
bde7418
update & fix dependencies (#3450)
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: