🚨🔥⚠️ 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 decreased (-2.3%) to 74.065% when pulling d78127619cdcc3db7179bcbcdd356ed4bacb6321 on greenkeeper-uglify-js-3.0.10 into ba48046f098b07baa069308ecd435e94b17a9f83 on master.
Hello lovely humans,
uglify-js just published its new version 3.0.10.
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 89 commits .
d3c4a8e
v3.0.10
7e164ab
add "es5" to package.json keywords (#1980)
22aedef
document minify() option
toplevel
(#1979)58fae7d
enhance
if_return
to handlereturn void...
(#1977)5bf8d7e
document 3.x minify() does not throw errors (#1975)
1df9d06
document minify
warnings
and add an error example (#1973)3408fc9
v3.0.9
eae2675
introduce
unsafe_regexp
(#1970)43add94
v3.0.8
efcf167
make
expect_stdout
node version specific (#1963)6ed9091
fix docs for side_effects flag to reflect current behavior (#1966)
569c21e
improve
RegExp
handling (#1959)87c3a2c
remove
space_colon
(#1960)baef8bf
update output options in readme (#1958)
0813c53
remove Travis CI badge
There are 89 commits in total. See the full diff.