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 gulp-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.
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 remained the same at 100.0% when pulling f451add360a09a2bd0b7a4adce41484b95344f21 on greenkeeper-gulp-uglify-2.1.2 into d6e7cb468f90ddad5c51d27f9cb607bc9d53ed57 on master.
Coverage remained the same at 100.0% when pulling 4d057c55d1d244f32fd51efa5dd100475ef5bd78 on greenkeeper-gulp-uglify-2.1.2 into b819723faa3a43d85204c7a729d9ccd47e2c9d5a on master.
Hello lovely humans,
gulp-uglify just published its new version 2.1.2.
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 gulp-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 :sparkles:
You rock!
:palm_tree:
GitHub Release
Bug Fixes
The new version differs by 22 commits .
4656fe5
2.1.2
ba83a45
fix(package): move eslint dependencies to dev
3d0f155
2.1.1
c722ab9
fix(errors): restore file and line info
da3e18f
chore(prettier): setup prettier
ec8ba54
fix(tests): UglifyJS errors use "message" property
6c336ec
v2.1.0
35c33f1
chore(uglifyjs): loosen uglify-js pin
74b6eff
2.0.1
832b427
chore(package): update uglify-js to version 2.7.5
1bf0f72
docs(README): link to Why Use Pump?
ccdc482
docs(pump): fix typo
5ddafd2
chore(package): update uglify-js to version 2.7.4
d5801ca
chore(greenkeeper): ignore "gulp-sourcemaps" dependency
129df84
chore(package.json): update repository field
There are 22 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.