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

[greenkeeper]

The devDependency commitizen was updated from 3.1.1 to 3.1.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 v3.1.2

3.1.2 (2019-07-17)

Bug Fixes

• deps: update dependency lodash to v4.17.14 [security] (#641) (1875a38), closes commitizen/cz-cli#639
• release fixed sem-release (#648) (4417fcf)
• update dependencies for security (#645) (b3dd4c4)

Commits

The new version differs by 5 commits.

• 4417fcf fix: release fixed sem-release (#648)
• b3dd4c4 fix: update dependencies for security (#645)
• 1875a38 fix(deps): update dependency lodash to v4.17.14 [security] (#641)
• 372c75e docs: highlight pre-requisties and bubble up related sections (#613)
• b24eade chore(security): fixed 5 vulnerabilities (#599)

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