FAQ
Frequently Asked Questions
Common questions about version generation and synchronization.
custy versionCategory
Quick Command
custy version updateOverview​
This page answers common questions about the Version command and how it fits into Custy's release workflow.
Does Version Update create a Git tag?
No.
The Version command only synchronizes version information inside the project.
Creating Git tags is handled separately by the Tag command.
Can I choose a different versioning strategy?
Yes.
Custy supports multiple versioning strategies, including:
- SemVer
- PEP 440
- Commitizen
- Date
- Git Count
The default strategy can be configured in config.toml, while command-line
options can temporarily override it for a single execution.
What happens if I provide --tag?
Providing --tag bypasses automatic version generation.
Custy uses the supplied version directly when synchronizing project files.
Does Version Update modify every project file?
No.
Custy updates only supported version files for the detected project type.
For example:
- Python projects update Python-related version files.
- Node.js projects update supported package metadata files.
Can I preview the changes first?
Yes.
Run:
custy --dry-run version update
to preview the synchronization process without modifying project files.
Can Version Update be used inside workflows?
Yes.
Version Update can be executed independently:
custy version update
Larger public profiles reuse the necessary version stages internally. There is
no public custy run apply_version form in the current CLI.
What if my project uses a different version file?
Custy does not require a fixed file location.
Configure the version file path inside config.toml, and Custy will update
that file during version synchronization.
Where should I go next?
Now that you understand Version Update, continue with the Commit documentation to learn how Custy records version changes in your Git history before creating tags and releases.