Skip to main content

Workflow

Workflow

Stable

Understand how Custy prepares, generates, and synchronizes project version information.

Commandcusty version

Category

Versioning

Quick Command

custy version update
workflowversion

Overview​

Version Update follows a structured workflow that validates the project, determines the next version, and synchronizes version information across the appropriate project files.

The same workflow is used whether the command is executed directly or as part of a larger workflow through custy run.

Version Update Workflow

High-level execution sequence.

1
Validate Project
Verify the project repository and any explicitly configured version target.
completed
2
Generate Version
Determine the next version using an explicit tag or the selected versioning strategy.
completed
3
Prepare Tag Message
Resolve or initialize the tag message template used by later workflow stages.
completed
4
Detect Project Type
Identify the target project ecosystem before synchronizing version files.
completed
5
Synchronize Project Files
Update every supported version file using the generated version.
completed

Workflow Stages

1. Validate Project
pending
2. Generate the Next Version
pending
3. Prepare the Tag Message
pending
4. Detect the Project Type
pending
5. Synchronize Version Files
pending

Workflow Execution

Larger public profiles reuse the necessary version stages internally. The internal apply_version profile name is not accepted by the current public Run argument, so standalone updates use custy version update.

What's Next?

Continue to the Examples page to see common Version Update scenarios and recommended workflows.