Title: cz bump recognizes wrong increment in Azure DevOps · commitizen-tools/commitizen · Discussion #965 · GitHub
Open Graph Title: cz bump recognizes wrong increment in Azure DevOps · commitizen-tools/commitizen · Discussion #965
X Title: cz bump recognizes wrong increment in Azure DevOps · commitizen-tools/commitizen · Discussion #965
Description: cz bump recognizes wrong increment in Azure DevOps
Open Graph Description: Hi all, Good day! I am incorporating "cz bump" for automated semantic versioning in our application. Unfortunately, "cz bump" does not work as expected. It recognizes the increment as "MAJOR" all t...
X Description: Hi all, Good day! I am incorporating "cz bump" for automated semantic versioning in our application. Unfortunately, "cz bump" does not work as expected. It recognizes the increm...
Opengraph URL: https://github.com/commitizen-tools/commitizen/discussions/965
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"QAPage","mainEntity":{"@type":"Question","name":"cz bump recognizes wrong increment in Azure DevOps","text":"Hi all,
\nGood day!
\nI am incorporating \"cz bump\" for automated semantic versioning in our application.
\nUnfortunately, \"cz bump\" does not work as expected.
\nIt recognizes the increment as \"MAJOR\" all the time irrespective of \"fix\" and \"feat\" commits only.
\nHowever, cz changelog shows the correct set of commits per version
\nCurrent version: 5.0.0\n## Unreleased\n\n### Fix\n\n- move only specific version\n\n## 4.0.0 (2024-01-18)\n### Feat\n\n- scm based ver moves\n- scm based ver moves\n- scm based ver moves\n- scm based ver moves\n\n### Fix\n\n- move only specific version\n- removed the extra line\n\n## 3.0.0 (2024-01-18)\n\n### Fix\n\n- removed verison write\n\n## 2.0.0 (2024-01-18)\n\n### Feat\n\n- test the ver increment\n### Fix\n\n- corrected at tag\n- branche names\n\n## 2.0.0a0 (2024-01-18)\n\n### BREAKING CHANGE\n\n- test\n\n### Feat\n\n- new lines\n- add PR based stage exec\n- add PR based stage exec\n\n### Fix\n\n- test the new config\n- test minor\n- Merged PR 30488: test\n- test minor\n- test minor\n\n
\nI 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
\nCould you please suggest how this issue can be resolved?
\nLooking forward to your responses :)
\nRegards,
\nRam
","upvoteCount":0,"answerCount":4,"acceptedAnswer":{"@type":"Answer","text":"@woile It works now.
\nIt was resolved with the setting \"fetchDepth: 1\" in Azure DevOps ci/cd yaml config :)
\nBy default, Azure DevOps fetch all the commits misleading cz bump.
\nfetchDepth needs to be configured accordingly to consider only the latest commits.
\n","upvoteCount":1,"url":"https://github.com/commitizen-tools/commitizen/discussions/965#discussioncomment-8172288"}}}
| route-pattern | /_view_fragments/Voltron::DiscussionsFragmentsController/show/:user_id/:repository/:discussion_number/discussion_layout(.:format) |
| route-controller | voltron_discussions_fragments |
| route-action | discussion_layout |
| fetch-nonce | v2:7afc4b86-36f9-8524-ad23-a3759143a534 |
| current-catalog-service-hash | 9f0abe34da433c9b6db74bffa2466494a717b579a96b30a5d252e5090baea7be |
| request-id | B6C0:959DF:1EA91AD:280ED4A:6976DA95 |
| html-safe-nonce | b0a5d1a9a6c7ec74680424652d4da8d269cfd461d795fb176f33b1fab9638d7e |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCNkMwOjk1OURGOjFFQTkxQUQ6MjgwRUQ0QTo2OTc2REE5NSIsInZpc2l0b3JfaWQiOiIzODUzNTMwNDY4ODkyMjAzNjY5IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 86313a9621f13dc34de27edebb513bdef6f6f0b3b52a618c279e69c2fba21cac |
| hovercard-subject-tag | discussion:6090918 |
| github-keyboard-shortcuts | repository,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/Voltron::DiscussionsFragmentsController/show/commitizen-tools/commitizen/965/discussion_layout |
| twitter:image | https://opengraph.githubassets.com/72088ddff600b0eab8ce977d70a610b7241d329f662b001ddc307886c817bf57/commitizen-tools/commitizen/discussions/965 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/72088ddff600b0eab8ce977d70a610b7241d329f662b001ddc307886c817bf57/commitizen-tools/commitizen/discussions/965 |
| og:image:alt | Hi all, Good day! I am incorporating "cz bump" for automated semantic versioning in our application. Unfortunately, "cz bump" does not work as expected. It recognizes the increment as "MAJOR" all t... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| hostname | github.com |
| expected-hostname | github.com |
| None | 01d198479908d09a841b2febe8eb105a81af2af7d81830960fe0971e1f4adc09 |
| turbo-cache-control | no-preview |
| go-import | github.com/commitizen-tools/commitizen git https://github.com/commitizen-tools/commitizen.git |
| octolytics-dimension-user_id | 62252524 |
| octolytics-dimension-user_login | commitizen-tools |
| octolytics-dimension-repository_id | 106127589 |
| octolytics-dimension-repository_nwo | commitizen-tools/commitizen |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 106127589 |
| octolytics-dimension-repository_network_root_nwo | commitizen-tools/commitizen |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | f752335dbbea672610081196a1998e39aec5e14b |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width