An in-range update of standard-version is breaking the build 🚨

[greenkeeper]

Version 4.3.0 of standard-version was just published.

Branch	Build failing 🚨
Dependency	standard-version
Current Version	4.2.0
Type	devDependency

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

standard-version 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

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 8 commits.

• 9a99607 chore(release): 4.3.0
• 4fd3bc2 feat: do not update/commit files in .gitignore (#230)
• c5e1ee2 feat: publish only if commit+push succeed (#229)
• 45fcad5 feat(format-commit-message): support multiple %s in the message
• b37bc66 test(format-commit-message): add failing test cases
• 3fdd7fa fix: use the skip default value for skip cli arg (#211)
• 709dae1 fix: recommend --tag prerelease for npm publish of prereleases (#196)
• 958daf4 chore: add link to community slack (#202)

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