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 decreased (-5.1%) to 85.714% when pulling 1737b365eca047d98e16c6ab4c7064e9fa8a0b4d on greenkeeper-gulp-uglify-2.1.0 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage decreased (-5.1%) to 85.714% when pulling 1737b365eca047d98e16c6ab4c7064e9fa8a0b4d on greenkeeper-gulp-uglify-2.1.0 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage decreased (-5.1%) to 85.714% when pulling 1737b365eca047d98e16c6ab4c7064e9fa8a0b4d on greenkeeper-gulp-uglify-2.1.0 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage decreased (-5.1%) to 85.714% when pulling 1737b365eca047d98e16c6ab4c7064e9fa8a0b4d on greenkeeper-gulp-uglify-2.1.0 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Hello lovely humans,
gulp-uglify just published its new version 2.1.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 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
Minor Fixes
The new version differs by 94 commits .
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
533ee01
fix(package): update uglify-js to version 2.7.3
1f2c508
docs(why-use-pump): fix plugin name
2829956
docs(README): fix typo
48bc2e3
chore(package): update vinyl to version 2.0.0
2c8c5a3
chore(package): update uglify-js to version 2.7.1
There are 94 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.