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

[greenkeeper[bot]]

Version 2.5.0 of gulp-sourcemaps just got published.

Branch	Build failing 🚨
Dependency	gulp-sourcemaps
Current Version	2.4.1
Type	devDependency

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

As gulp-sourcemaps 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 :muscle:

---

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/marcobiedermann/wordpress-theme-boilerplate/builds/216144000)

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

Version 2.5.1 just got published.

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

[greenkeeper[bot]]

Version 2.5.2 just got published.

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

Commits

The new version differs by 3 commits .

• 8039c13 2.5.2
• ee64234 Update organization references (closes #289)
• 9857f3f Logging Improvements (#301)

See the full diff.

[greenkeeper[bot]]

Version 2.6.0 just got published.

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

Commits

The new version differs by 2 commits .

• 65d099a 2.6.0
• 44801fa Deprecate options.identityMap and export identityMap stream (#303)

See the full diff.