cz bump recognizes wrong increment in Azure DevOps #965
|
Hi all, Good day! I am incorporating "cz bump" for automated semantic versioning in our application. Unfortunately, "cz bump" does not work as expected. However, cz changelog shows the correct set of commits per version I suppose "cz bump" keeps taking all the commits including "BREAKING CHANGE" which is part of the version 2.0.0a0 and recognize as MAJOR increment all the time Could you please suggest how this issue can be resolved? Looking forward to your responses :) Regards, |
Replies: 4 comments 6 replies
|
Please provide steps to reproduce |
|
Steps to reproduce: Current version: 5.0.0 pyproject.toml cz bump command: My commits format: Looking into the source code of "get_commits()" method |
|
@woile It works now. It was resolved with the setting "fetchDepth: 1" in Azure DevOps ci/cd yaml config :) By default, Azure DevOps fetch all the commits misleading cz bump. |
|
@woile It works now.
It was resolved with the setting "fetchDepth: 1" in Azure DevOps ci/cd yaml config :)
By default, Azure DevOps fetch all the commits misleading cz bump.
fetchDepth needs to be configured accordingly to consider only the latest commits.
Ref:
https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/steps-checkout?view=azure-pipelines