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

[greenkeeper[bot]]

The devDependency gulp-load-plugins was updated from 1.5.0 to 1.6.0.

🚨 View failing branch.

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

gulp-load-plugins is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/loginov-rocks/Angular-Gulp-Boilerplate/builds/539333679?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 4 commits.

• 2e24542 1.6.0
• d979a96 bump mocha to fix security issue
• 595ab83 Bump packages on vulnerability paths (#138)
• 174cd3b Fix ESLint error (#133)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[greenkeeper[bot]]

• The devDependency gulp-load-plugins was updated from 2.0.0 to 2.0.1.

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

[greenkeeper[bot]]

• The devDependency gulp-load-plugins was updated from 2.0.2 to 2.0.3.

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

Release Notes for v2.0.3

Updating dependencies