🚨🔥⚠️ 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 0858a9f0974d17f833545f52d77a736ce4191c33 on greenkeeper-uglify-js-3.0.6 into ed26feceb117953e5dc4232a0d9600f18df200f9 on master.
Hello lovely humans,
uglify-js just published its new version 3.0.6.
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 522 commits .
050474a
v3.0.6
f6c805a
print package name alongside version in CLI (#1946)
9464d3c
fix parsing of property access after new line (#1944)
f18abd1
minor fixes to README.md
3be06ad
reorg README for 3.x (#1942)
265008c
improve keyword-related parser errors (#1941)
ff526be
v3.0.5
e005099
fix & improve coverage of
estree
(#1935)504a436
Tweak README Notes (#1934)
3ca9022
fix bugs with getter/setter (#1926)
fd09512
document 3 max passes (#1928)
9e29b6d
clarify wording (#1931)
c391576
remove support for
const
(#1910)ac73c5d
avoid
arguments
andeval
inreduce_vars
(#1924)547f41b
add documentation for
side_effects
&[#@]__PURE__
(#1925)There are 250 commits in total. See the full diff.