🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
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.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of uglify-js.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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.
Coverage remained the same at 100.0% when pulling 7969ba782b19823ba45e7cd8b2092ef26a50ee5a on greenkeeper-uglify-js-3.0.12 into ed26feceb117953e5dc4232a0d9600f18df200f9 on master.
Hello lovely humans,
uglify-js just published its new version 3.0.12.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of uglify-js. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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:
GitHub Release
The new version differs by 555 commits .
c3f14a1
v3.0.12
7b13159
fix
hoist_funs
on block-scopedfunction
under "use strict" (#2013)95094b9
fix
if_return
onAST_Defun
(#2010)1ff8e9d
clarify what --mangle-props does (#2012)
78309a2
better document mangle properties options (#2009)
695e182
fix and expand --mangle-props documentation (#2008)
dc33fac
fix
dead_code
on block-scopedfunction
under "use strict" (#2006)c70fb60
clean up
lib/scope.js
(#2003)793d614
report timing breakdown (#2000)
a277fe1
ensure new line after
describe_ast()
(#1999)7d3b941
reinstate
describe_ast()
on CLI (#1996)e95052a
v3.0.11
e667f0a
fix source map offset (#1993)
69ac794
add another minify() options example (#1988)
efdb659
improve usability of
global_defs
inminify()
(#1987)There are 250 commits in total. See the full diff.