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

[greenkeeper]

The devDependency commitizen was updated from 3.0.2 to 3.0.3.

🚨 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

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for v3.0.3

<a name"3.0.3">

3.0.3 (2018-10-19)

Bug Fixes

• config loader: deal with config file charset (#525) (c74eeb9e)

Commits

The new version differs by 4 commits.

• c74eeb9 fix(config loader): deal with config file charset (#525)
• 42c8bb6 docs: fix link to external adapter (#581)
• 9e05c28 docs: add esg github adapter to the docs (#579)
• 2965fe6 docs: add another JIRA adapter (#576)

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