-
Notifications
You must be signed in to change notification settings - Fork 3
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 🚨 #12
Comments
Version 2.8.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 6 commits .
See the full diff. |
Version 2.8.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.8.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.8.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 9 commits .
See the full diff. |
Version 2.8.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 12 commits .
See the full diff. |
Version 2.8.7 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.8.8 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits .
See the full diff. |
Version 2.8.9 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.8.10 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 2.8.11 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.11
CommitsThe new version differs by 10 commits .
See the full diff. |
Version 2.8.12 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.12
CommitsThe new version differs by 14 commits .
See the full diff. |
Version 2.8.13 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.13
CommitsThe new version differs by 22 commits .
There are 22 commits in total. See the full diff. |
Version 2.8.14 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.14
CommitsThe new version differs by 30 commits .
There are 30 commits in total. See the full diff. |
Version 2.8.15 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.15
CommitsThe new version differs by 36 commits .
There are 36 commits in total. See the full diff. |
Version 2.8.16 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.16
CommitsThe new version differs by 48 commits .
There are 48 commits in total. See the full diff. |
Version 2.8.17 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.17
CommitsThe new version differs by 74 commits .
There are 74 commits in total. See the full diff. |
Version 2.8.18 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.18
CommitsThe new version differs by 77 commits .
There are 77 commits in total. See the full diff. |
Version 2.8.19 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.19
CommitsThe new version differs by 87 commits .
There are 87 commits in total. See the full diff. |
Version 2.8.20 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.20
CommitsThe new version differs by 89 commits .
There are 89 commits in total. See the full diff. |
Version 2.8.21 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.21
CommitsThe new version differs by 104 commits .
There are 104 commits in total. See the full diff. |
Version 2.8.22 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.8.22
CommitsThe new version differs by 125 commits .
There are 125 commits in total. See the full diff. |
Version 2.8.0 of uglify-js just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As uglify-js is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
❌ coverage/coveralls Coverage pending from Coveralls.io Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 48 commits .
0b0296e
v2.8.0
872270b
improve error messages (#1506)
b1c593a
add harmony branch details in README (#1507)
13be50a
faster tree transversal (#1462)
16cd5d5
consolidate
evaluate
&reduce_vars
(#1505)834f9f3
update docs for
pure_funcs
&drop_console
(#1503)cf0951f
allow --in-source-map inline (#1490)
852f784
Avoid using exports when undefined (#1471)
229e42c
Merge pull request #1485 from alexlamsl/merge-2.8.0
4e49302
enable
collapse_vars
&reduce_vars
by default1e51586
Support marking a call as pure
d48a308
Fix: AST_Accessor missing start / end tokens
26fbeec
fix
pure_funcs
& improveside_effects
8898b8a
clean up
max_line_len
ec64acd
introduce
unsafe_proto
There are 48 commits in total. 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 🌴
The text was updated successfully, but these errors were encountered: