release

📋 TEMPLATE: This command uses {{MAIN_BRANCH}}, {{TICKET_PREFIX}}, and {{GITHUB_ORG}}/{{GITHUB_REPO}} placeholders. Replace with your project values.

You are executing a full version release. Follow each phase in order. Do not skip phases. Report status after each.

Input

The user provides a version number (e.g., v2.7.0). If not provided, determine the next version by:

git tag -l 'v*' | sort -V | tail -1

Then bump the minor version (or ask the user for major/minor/patch).

---

Phase 1: Pre-Release Validation

1.1 Verify Clean State

git status                    # Must be clean
git branch --show-current     # Must be on {{MAIN_BRANCH}}
git fetch origin
git log --oneline origin/{{MAIN_BRANCH}}..HEAD  # Must be empty (in sync)

BLOCKER: Working tree must be clean and branch must be current with remote.

1.2 Check Open PRs

gh pr list --state open

Decision point: If there are open PRs intended for this release, merge them first (Phase 2). If none, skip to Phase 3.

1.3 Verify CI Status

For each open PR to merge:

gh pr view <NUMBER> --json mergeStateStatus,statusCheckRollup \
  --jq '{state: .mergeStateStatus, checks: [.statusCheckRollup[] | "\(.name): \(.conclusion // .status)"]}'

BLOCKER: All checks must pass. Do not merge PRs with failing required checks.

---

Phase 2: Merge Open PRs (if any)

2.1 Merge in Dependency Order

For each PR (merge in order — base dependencies first):

# Squash merge with proper commit message
gh pr merge <NUMBER> --squash --subject "type(scope): description [{{TICKET_PREFIX}}-XXX]"

2.2 Rebase Dependent PRs

After each merge, rebase any remaining PRs that target the same base:

git fetch origin
git checkout <dependent-branch>
git rebase origin/{{MAIN_BRANCH}}
git push --force-with-lease origin <dependent-branch>

Wait for CI to re-run before merging the next PR.

2.3 Sync Local After All Merges