An in-range update of cloudinary-core is breaking the build 🚨

[greenkeeper]

The dependency cloudinary-core was updated from 2.7.4 to 2.8.0.

🚨 View failing branch.

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

cloudinary-core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build errored.

---

Release Notes for Version 2.8.0

New functionality and features

• Add support for signature option to url function (#198)

Other Changes

• Add npm package test (#187)
• Fix lodash imports
• Fix responsive and minified tests
• Fix files list for npm package in package.json

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 2.7.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The dependency cloudinary-core was updated from 2.8.0 to 2.8.1.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The dependency cloudinary-core was updated from 2.8.1 to 2.8.2.

Your tests are still failing with this version. Compare changes

Release Notes for Version 2.8.2

• Fix - Add signature to list of url keys so that extractUrlParams() won't filter it
• Add test for package size using bundlewatch