Preparing Releases
Preparing Releases
Bergerak dari approved release state melalui version, changelog, commit, tag, dan remote publication.
custy run releaseCategory
Quick Command
custy --dry-run run release [OPTIONS]Tujuan
Gunakan Release ketika approved version harus diterapkan, didokumentasikan, di-commit, diberi tag, dan di-push. Profile memvalidasi release prerequisites dan berakhir setelah push; profile tidak menjalankan experimental finalization stage milik Full.
Release Readiness Checklist
Before You Begin
- The release scope is approvedRequired
Included changes, version intent, dan publication timing telah disepakati.
- Messages are reviewedRequired
Commit dan tag message files tersedia dan memenuhi configured convention.
- Version configuration is correctRequired
Tinjau version file, strategy, bump behavior, dan explicit tag input.
- Changelog policy is understoodRequired
Konfirmasi templates, mappings, final-version behavior, dan output path.
- Every remote is verifiedRequired
Periksa origin, primary, backup, dan synchronization policy sebelum publication.
- Recovery is plannedRequired
Ketahui cara memeriksa partial file update, commit, tag, atau multi-remote push.
git status --short --branch
git diff
git diff --staged
git tag --list
git remote -v
custy validateRecommended Release Journey
Reviewed Publication
custy --dry-run run release
custy run releaseRelease Completion Boundaries
State yang Harus Diverifikasi
Project Files
Recovery Files
Local Git
Remote State
Release Pipeline mendokumentasikan exact 24-step sequence. Changelog generation tersedia dalam sequence tersebut, tetapi tetap dapat dilewati oleh active final-version dan configuration rules.
Post-Release Verification
git status --short --branch
git log -1 --decorate --stat
git tag --points-at HEAD
git remote -vVerifikasi juga branch dan tag melalui setiap repository host atau appropriate fetch-and-compare process. Successful push ke satu destination tidak membuktikan seluruh configured destinations selesai.