You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, using PEP 621, the version needs to be stored in pyproject.toml in two locations:
project.version
tool.commitizen.version
Running cz bump modifies only tool.commitizen.version, leaving the two out of sync. project.version is arguably the correct place to store this metadata for anything outside of commitizen's purview.
Possible Solution
A config item / CLI option could be added to specify that commitizen should only operate on project.version.
Example:
Description
Currently, using PEP 621, the version needs to be stored in pyproject.toml in two locations:
project.version
tool.commitizen.version
Running
cz bump
modifies onlytool.commitizen.version
, leaving the two out of sync.project.version
is arguably the correct place to store this metadata for anything outside of commitizen's purview.Possible Solution
A config item / CLI option could be added to specify that commitizen should only operate on
project.version
.Example:
The text was updated successfully, but these errors were encountered: