Skip to main content

Full Pipeline

Full Pipeline

Experimental Finalization

Run the complete Release sequence and then invoke experimental workflow finalization after publication.

Commandcusty run full

Category

Pipeline Profile

Quick Command

custy run full [OPTIONS]

releasepushbranch finalization

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.

Preview with extra care
bash
custy --dry-run run full
custy run full

Exact Phase Flow

Full Profile

1
Validate release prerequisites
Run repository, pre-commit, pre-tag, and pre-push checks.
completed
2
Prepare and review
Resolve version and workflow state, prepare messages, generate artifacts, and validate edits.
completed
3
Apply and document
Apply the version and run conditional changelog generation.
completed
4
Back up and clean
Back up commit and tag messages and apply retention cleanup.
completed
5
Commit, tag, and push
Create and publish the release through the same stages used by Release.
completed
6
Finalize workflow
Invoke the experimental post-release branch workflow for the resolved case.
current

Exact Full Step Order

Steps 1–24 are identical to Release; finalization is step 25.

01–09Run the nine release validations listed in the Release Pipeline.
10 — prepare_version_stepResolve the release version and tag context.
11 — workflow_init_stepInitialize branch workflow state.
12 — prepare_tag_message_stepPrepare the tag message.
13 — generate_artifacts_stepGenerate configured release artifacts.
14 — edit_files_stepOpen artifacts for review and editing.
15 — validate_edited_stepValidate the edited artifacts.
16 — apply_version_stepApply the resolved version.
17 — generate_changelog_stepRun conditional changelog generation.
18 — backup_commit_message_files_stepBack up the commit message.
19 — backup_tag_message_files_stepBack up the tag message.
20 — cleanup_backup_stepApply backup retention cleanup.
21 — stage_stepStage the release files.
22 — commit_stepCreate the release commit.
23 — tag_stepCreate the local release tag.
24 — push_stepPublish HEAD and the eligible release tag.
25 — finalize_stepInvoke 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.


Continue