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

[greenkeeper]

The devDependency commitizen was updated from 3.0.7 to 3.1.0.

🚨 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.0

3.1.0 (2019-04-18)

Features

• cli: Implement --hook option for git hooks integration (#615) (26533fc), closes #448 #462

Commits

The new version differs by 2 commits.

• 26533fc feat(cli): Implement --hook option for git hooks integration (#615)
• 515a57e docs(readme): document behavior of npx git-cz in non-Commitizen friendly repository (#612)

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

[greenkeeper]

• The devDependency commitizen was updated from 3.1.0 to 3.1.1.

Your tests are still failing with this version. Compare changes

Release Notes for v3.1.1

3.1.1 (2019-04-19)

Bug Fixes

• cli: allow argv to be overridden in bootstrap (#621) (f7982d3)

Commits

The new version differs by 1 commits.

• f7982d3 fix(cli): allow argv to be overridden in bootstrap (#621)

See the full diff