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

[greenkeeper]

The devDependency commitizen was updated from 4.0.1 to 4.0.2.

🚨 View failing branch.

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

commitizen 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 could not complete due to an error (Details).

---

Release Notes for v4.0.2

4.0.2 (2019-07-19)

Bug Fixes

• deps: update dependency lodash to v4.17.15 (#652) (129a779)

Commits

The new version differs by 3 commits.

• 129a779 fix(deps): update dependency lodash to v4.17.15 (#652)
• 5f71dfe Adding tasks to publish test results to AzurePipelines (#590)
• f5751b2 chore: update mocha, other dev deps (#653)

See the full diff

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 4.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.