An in-range update of bower is breaking the build 🚨

[greenkeeper]

Version 1.8.1 of bower just got published.

Branch	Build failing 🚨
Dependency	bower
Current Version	1.8.0
Type	dependency

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

bower is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

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]

After pinning to 1.8.0 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

Version 1.8.2 just got published.

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

[greenkeeper]

Version 1.8.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

[greenkeeper]

Version 1.8.4 just got published.

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

Release Notes

v1.8.4

• Fixes release 1.8.3 by publishing with npm@3 instead of npm@5 (to include lib/node_modules)

[greenkeeper]

• The dependency bower was updated from 1.8.4 to 1.8.6.

Your tests are still failing with this version. Compare changes

Release Notes for v1.8.6

Fix Zip Slip Vulnerability of decompress-zip package: https://snyk.io/research/zip-slip-vulnerability

Note: v1.8.5 has been unpublished because of missing files

[greenkeeper]

• The dependency bower was updated from 1.8.6 to 1.8.7.

Your tests are still failing with this version. Compare changes

Release Notes for v1.8.7

Fixes side effect of fix from v1.8.6 that caused improper permissions for extracted folders

#2532