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

[greenkeeper]

Version 1.1.2 of gulp-istanbul just got published.

Branch	Build failing 🚨
Dependency	gulp-istanbul
Current Version	1.1.1
Type	devDependency

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

As gulp-istanbul 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/appveyor/branch Waiting for AppVeyor build to complete Details
• ❌ ci/circleci Your tests failed on CircleCI Details

---

Release Notes

v1.1.2

• Bump dependencies

Commits

The new version differs by 6 commits.

• 502855e 1.1.2
• ac8f966 Add documentation for reportOpts and watermarks (#121)
• be326d1 Update README.md to warn about gulp-mocha (#120)
• b0149ac fix(package): update istanbul-threshold-checker to version 0.2.1 (#112)
• 7ec737a chore(package): update dependencies (#110)
• b047c82 Update .travis.yml

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 1.1.3 just got published.

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

Release Notes

v1.1.3

Fix deprecated gulp-utils usage

Commits

The new version differs by 3 commits.

• 6ea01ce 1.1.3
• 7b74390 replaced deprecated gulp-util and fixed broken test (#129)
• 1e3adcb chore(package): update mocha to version 4.0.0 (#126)

See the full diff