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

[greenkeeper]

Version 4.4.0 of standard-version was just published.

Branch	Build failing 🚨
Dependency	standard-version
Current Version	4.3.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

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 8 commits.

• e5c99f6 chore(release): 4.4.0
• 04c68a8 chore: npm audit (#244)
• ba4e7f6 feat: add prerelease lifecycle script hook (closes #217) (#234)
• b4ed4f9 fix: show full tag name in checkpoint (#241)
• fbfdf5e doc : added an example of a postcommit hook (#232)
• 371d992 feat: manifest.json support (#236)
• 6dac27b docs: add title to LICENSE.txt (#238)
• a56c7ac fix: use tagPrefix in CHANGELOG lifecycle step (#243)

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