# Commitizen-galaxy-provider — a Commitizen version provider for galaxy.yml **URL:** \ **Category:** Project Discussions\ **Tags:** ansible-galaxy, collections, galaxy-ng\ **Created:** [September 24, 2026, 7:14am UTC](https://forum.ansible.com/t/commitizen-galaxy-provider-a-commitizen-version-provider-for-galaxy-yml/46353 "2026-09-24T07:14:11Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Shaps](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shaps/32/1356_2.png) [@Shaps](https://forum.ansible.com/u/Shaps)\ **Post date:** [September 24, 2026, 7:14am UTC](https://forum.ansible.com/t/commitizen-galaxy-provider-a-commitizen-version-provider-for-galaxy-yml/46353/1 "2026-09-24T07:14:11Z")
I use [Commitizen](https://commitizen-tools.github.io/commitizen/) for conventional commits on all projects at work, and as we migrated to collections, we couldn’t find a practical way to manage versions when pushing to automation hub. Commitizen didn’t have a provider for galaxy.yml out of the box, so I wrote one: commitizen-galaxy-provider. Set it as your `version_provider` and `cz bump` will read and write the version field in `galaxy.yml` directly, leaving every other field (namespace, authors, dependencies, etc.) untouched. Install: `uv add commitizen commitizen-galaxy-provider` or `pip install commitizen commitizen-galaxy-provider` Configure in pyproject.toml: ```toml [tool.commitizen] version_provider = "galaxy" ``` Then cz bump handles version bumping and tagging for the collection the same way it would for a Python package. Source: [GitHub - Shaps/commitizen-galaxy-provider: A (ansible) Galaxy provider for commitizen. · GitHub](https://github.com/Shaps/commitizen-galaxy-provider) PyPI: [commitizen-galaxy-provider · PyPI](https://pypi.org/project/commitizen-galaxy-provider/) Sharing in case it’s useful to anyone else running Commitizen against a collection. Feedback welcome.