search

pvdlg / cz-conventional-commit

Commitizen adapter following the conventional-changelog format, with emojis. 🎉
MIT License
16 stars 10 forks source link

An in-range update of conventional-commits-parser is breaking the build 🚨 #67

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

The devDependency conventional-commits-parser was updated from 3.0.3 to 3.0.5.

🚨 View failing branch.

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

conventional-commits-parser 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](https://travis-ci.org/pvdlg/cz-conventional-commit/builds/595525458?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 25 commits.

  • 7c1c8ad Publish
  • c493556 chore(deps): lock file maintenance
  • bfeed12 Publish
  • 4ec6f41 chore(conventional-changelog-writer): bump handlebars to 4.4.0 (#528)
  • 2de0195 chore(deps): lock file maintenance
  • faa2819 docs(readme): fix typo (#524)
  • 7a60dec fix: use full commit hash in commit link
  • b63a5ff fix(preset, eslint): display short tag in release notes
  • c0566ce fix(preset, conventionalcommits): fix handling conventionalcommits preset without config object
  • 417139c revert: "fix(preset-loader): fix handling conventionalcommits preset without config object" (#520)
  • a3acc32 feat: sort sections of CHANGELOG based on priority (#513)
  • 6425972 fix(preset-loader): fix handling conventionalcommits preset without config object
  • 958d243 fix(preset, conventionalcommits): pass issuePrefixes to parser (#510)
  • 1ed96fd docs: Update README.md (#508)
  • c0bac28 fix(deps): update dependency tempfile to v3 (#459)

There are 25 commits in total.

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

After pinning to 3.0.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.