An in-range update of gulp-uglify is breaking the build 🚨

[greenkeeper]

Version 2.1.1 of gulp-uglify just got published.

Branch	Build failing 🚨
Dependency	gulp-uglify
Current Version	2.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As gulp-uglify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.1.1

Bug Fixes

• errors: restore filenames and line information to GulpUglifyError's toString method. (c722ab9c)

Commits

The new version differs by 3 commits .

• 3d0f155 2.1.1
• c722ab9 fix(errors): restore file and line info
• da3e18f chore(prettier): setup prettier

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 2.1.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

v2.1.2

Bug Fixes

• package: In the previous release devDependencies were incorrectly added as dependencies. This moves them to the correct location. (ba83a45c)

Commits

The new version differs by 2 commits .

• 4656fe5 2.1.2
• ba83a45 fix(package): move eslint dependencies to dev

See the full diff.