-
Notifications
You must be signed in to change notification settings - Fork 2
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 🚨 #32
Comments
After pinning to 3.5.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.4
|
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.5
|
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.6
CommitsThe new version differs by 12 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.7
CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.8
CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.9
CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.10
CommitsThe new version differs by 29 commits.
There are 29 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.11
CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.12
CommitsThe new version differs by 40 commits.
There are 40 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.13
CommitsThe new version differs by 48 commits.
There are 48 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.14
CommitsThe new version differs by 50 commits.
There are 50 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.5.15
CommitsThe new version differs by 52 commits.
There are 52 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.6.0
CommitsThe new version differs by 55 commits.
There are 55 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.6.1
CommitsThe new version differs by 65 commits.
There are 65 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.6.2
CommitsThe new version differs by 74 commits.
There are 74 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.6.3
CommitsThe new version differs by 92 commits.
There are 92 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 103 commits.
There are 103 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.6.5
CommitsThe new version differs by 15 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.6.6
CommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.6.7
CommitsThe new version differs by 30 commits.
There are 30 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.6.8
CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
The devDependency uglify-js was updated from
3.5.2
to3.5.3
.🚨 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.5.3
Commits
The new version differs by 3 commits.
fa43768
v3.5.3
a74e600
mangle shadowed lambda under
ie8
correctly (#3356)4b21526
Fix test expectation (#3357)
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: