Feature Request: Option To Automatically Update Major and Minor Version Tags #23

Activity

1. woile commented on Mar 3, 2023

   

   woile

   on Mar 3, 2023

   Member

   More actions

   You would like this action to offer v1, v2, etc. Or for this action to create 2 tags? one with the x.y.z and another with just x? for the later I think we need 2 changes:

   in commitizen

   add to the cz version a flag to get the different chunks, like cz version --project --format 'v$MAJOR'

   in commitizen-action

   add a flag "major_tag" which would execute:

   if [[ $INPUT_MAJOR_TAG == 'true' ]]; then
       git tag $(cz version --project --format 'v$MAJOR')
   fi

   I'm open to this feature, but I don't have the capacity to add the flag to commitizen, PRs are welcome
2. Kurt-von-Laven commented on Mar 3, 2023

   

   Kurt-von-Laven

   on Mar 3, 2023

   ContributorAuthor

   More actions

   2 tags (or 3 if we also include minor version) would be in keeping with GitHub Actions' guidance. I think it's okay to leave this open in case someone is interested in working on it eventually.
3. bearomorphism commented on May 10, 2026

   

   bearomorphism

   on May 10, 2026

   More actions

   Triage: feature request — auto-update floating vX and vX.Y tags so users can pin to e.g. commitizen-tools/commitizen-action@v0 and get patch/minor updates.

   Out of scope for the bug/doc sweep I'm doing today; leaving for maintainer review.

   Note that this repo itself already does this via the ci/publish-major-minor-tag workflow added in #88, so users can already pin to commitizen-tools/commitizen-action@0 or @0.27. The remaining ask is to also expose this behaviour as an opt-in input for users' own bump jobs.