Full Pipeline
Full Pipeline
Run the complete Release sequence and then invoke experimental workflow finalization after publication.
custy run fullCategory
Quick Command
custy run full [OPTIONS]Overviewâ
Full uses the complete Release step list and adds finalize_step at the end.
Finalization can perform branch transitions, merges, pushes, or cleanup according
to the workflow case discovered earlier in the pipeline.
custy --dry-run run full
custy run fullExact Phase Flow
Full Profile
Exact Full Step Order
Steps 1â24 are identical to Release; finalization is step 25.
| 01â09 | Run the nine release validations listed in the Release Pipeline. |
|---|---|
| 10 â prepare_version_step | Resolve the release version and tag context. |
| 11 â workflow_init_step | Initialize branch workflow state. |
| 12 â prepare_tag_message_step | Prepare the tag message. |
| 13 â generate_artifacts_step | Generate configured release artifacts. |
| 14 â edit_files_step | Open artifacts for review and editing. |
| 15 â validate_edited_step | Validate the edited artifacts. |
| 16 â apply_version_step | Apply the resolved version. |
| 17 â generate_changelog_step | Run conditional changelog generation. |
| 18 â backup_commit_message_files_step | Back up the commit message. |
| 19 â backup_tag_message_files_step | Back up the tag message. |
| 20 â cleanup_backup_step | Apply backup retention cleanup. |
| 21 â stage_step | Stage the release files. |
| 22 â commit_step | Create the release commit. |
| 23 â tag_step | Create the local release tag. |
| 24 â push_step | Publish HEAD and the eligible release tag. |
| 25 â finalize_step | Invoke experimental post-release branch workflow behavior. |
The Complete Profile Reference lists all 25 internal names individually. The grouping above keeps this page readable while making Full's one-step difference from Release immediately visible.
Use Full Only When
Before You Begin
- Release is already appropriateRequired
All version, changelog, commit, tag, and push requirements are satisfied.
- The branch workflow is understoodRequired
You know the detected workflow case and its final branch operations.
- Every destination is reviewedRequired
Origin, backup synchronization, and branch cleanup targets are correct.
- A dry-run has been reviewedRequired
You have inspected the planned release and branch operations.
- Recovery is manual and deliberateRequired
You can reconcile a release that succeeded before finalization failed.
Prefer Release by Default
Choose custy run release when you need a complete tagged publication but do
not need branch lifecycle finalization. It has the same release stages and a
clearer completion boundary: push.