Hello lovely humans,
grunt-contrib-uglify just published its new version 2.0.0.
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 grunt-contrib-uglify.
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 ✨
The new version differs by 12 commits .
Update uglify to v2.7.0. (#416)
Reduce lodash usage. (#422)
Used grunt.verbose to show detailed logging (#419) r=vladikoff
v1.0.2. (#423) r=vladikoff
Report option: false value is not supported.
Merge pull request #418 from gruntjs/beautify-obj
Fix beautify when passed as an object.
Update test files for the latest 2.6.4 version.
Update CI configs from the latest grunt-contrib-internal.
Upgrade grunt and devDeps to 1.0
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡️ greenkeeper upgrade
Might be useful, need to research whats different in Uglify 2 and if it breaks the dist files in any way.
chore(package): update grunt-contrib-uglify to version 2.0.0
Merge branch 'master' into greenkeeper-grunt-contrib-uglify-2.0.0