Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update uglify-js to version 2.7.3 🚀 #3547

Merged
merged 2 commits into from
Aug 17, 2016
Merged

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

uglify-js just published its new version 2.7.3.

State Update 🚀
Dependency uglify-js
New version 2.7.3
Type devDependency

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 ✨

You rock!

🌴


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@gkatsev
Copy link
Member

gkatsev commented Aug 17, 2016

LGTM

@gkatsev gkatsev force-pushed the greenkeeper-uglify-js-2.7.3 branch from 27cf0ad to d4be694 Compare August 17, 2016 21:53
@gkatsev gkatsev merged commit 46058dd into master Aug 17, 2016
@gkatsev gkatsev deleted the greenkeeper-uglify-js-2.7.3 branch August 17, 2016 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants