Release Core

If any are missing: STOP and report what's needed.

Phase 1: Verify Release Branch

git checkout release/X.Y.0
git pull origin release/X.Y.0
git status  # Must be clean

make release-check

If make release-check fails: STOP and report failures.

Phase 2: Update Versions

# Update boilerplate pinning
make release-set-core-ref REF=vX.Y.0

Manually edit these files:

Phase 3: Commit and PR to Develop

git add -A
git commit -m "chore(release): prepare vX.Y.0"
git push origin release/X.Y.0

Create PR:

cat > /tmp/pr-body.md <<'EOF'
## Release vX.Y.0

### Features
- [Feature 1] (#WO-NNN)
- [Feature 2] (#WO-NNN)

### Verification
- `make release-check` passed
- All Work Orders complete

Refs #NNN (Version Declaration)
EOF

gh pr create \
  --base develop \
  --head release/X.Y.0 \
  --title "Release vX.Y.0" \
  --body-file /tmp/pr-body.md

Report to user:

Release PR created: [link]

Please:
1. Run release audit
2. Review and squash-merge when ready
3. Reply "merged to develop" to continue

WAIT for user confirmation before proceeding.

Phase 4: PR Develop to Main

After user confirms merge to develop:

git checkout develop
git pull origin develop

Create PR to main:

cat > /tmp/pr-body.md <<'EOF'
## Release vX.Y.0

Production release of vX.Y.0.

### Changes
- [Summary of changes]

### Pre-merge Verification
- `make release-check` passed
- Release audit passed
EOF

gh pr create \
  --base main \
  --head develop \
  --title "Release vX.Y.0" \
  --body-file /tmp/pr-body.md

Report to user:

PR to main created: [link]

Please review and squash-merge.
Reply "merged to main" to continue with sync and tag.

WAIT for user confirmation before proceeding.

Phase 5: Sync and Tag

After user confirms merge to main:

git checkout main
git pull origin main

python scripts/sync_to_public.py \
  --public-repo-url [email protected]:markashton480/sum-core.git \
  --version vX.Y.0

This script:

1. Clones/updates sum-core to /tmp/sum-core-sync
2. Copies allowed paths
3. Commits and pushes
4. Creates annotated tag
5. Pushes tag

Phase 6: Verification

# Verify tag exists
git ls-remote --tags [email protected]:markashton480/sum-core.git | grep vX.Y.0

# Test scaffolding
cd /tmp
sum init test-release-vX.Y.0
cd test-release-vX.Y.0
sum check

# Test pip install
python -m venv /tmp/test-venv
source /tmp/test-venv/bin/activate
pip install "sum_core @ git+https://github.com/markashton480/[email protected]"
python -c "import sum_core; print(f'Version: {sum_core.__version__}')"
deactivate

# Cleanup
rm -rf /tmp/test-release-vX.Y.0 /tmp/test-venv /tmp/sum-core-sync

Phase 7: Report Success

Release vX.Y.0 complete!

Tag: https://github.com/markashton480/sum-core/releases/tag/vX.Y.0
- Scaffolding verified
- pip install verified

Next steps:
- Close Version Declaration issue
- Clean up feature branches (optional)
- Announce release (if applicable)

Error Handling

Pre-flight fails

Release blocked

Missing:
- [ ] Version Declaration #NNN
- [ ] Work Order #NNN not Done
- [ ] release/X.Y.0 branch doesn't exist

Please resolve before releasing.

Release check fails

make release-check failed

Failures:
- [specific failures]

Fix issues on release/X.Y.0 and try again.

Sync fails

Sync to sum-core failed

Error: [details]

Please resolve and reply "retry sync".

Tag exists

Tag vX.Y.0 already exists

Options:
1. Use next patch: vX.Y.1
2. Investigate why tag exists

Reply with choice.

Safety Rules

1. Never force-push tags - Create new patch version instead
2. Never skip checks - make release-check must pass
3. Always wait for human - Do NOT merge PRs automatically
4. Verify before reporting success - Run scaffolding test