This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage decreased (-2.2%) to 97.766% when pulling b4c2fa5b9d15e80fd06e081846958143216706fe on greenkeeper-uglify-js-2.8.10 into ac6d2f4dec769bd6f8c8feb7950e98c06f7d9f35 on master.
Hello lovely humans,
uglify-js just published its new version 2.8.10.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 117 commits .
e9920f7
v2.8.10
7e465d4
scan RHS of dropped assignments (#1581)
aa80ee3
remove checkboxes from Issues template
80e8176
explain how to make a proper bug report (#1579)
711f88d
scan assignment value in drop_unused() (#1578)
344d11d
v2.8.9
c7cdcf0
fix function name eliminiation (#1576)
3ee5574
only run benchmark & jetstream on CI (#1571)
dedbeef
plan B for IE8 do-while semi-colon fix (#1572)
bd6dee5
fix return from recursive IIFE (#1570)
144052c
v2.8.8
65c848c
include benchmark.js in test suite (#1564)
8a8a94a
fix deep cloning of labels (#1565)
8153b7b
transform function calls to IIFEs (#1560)
d787d70
avoid substitution of global variables (#1557)
There are 117 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.