post-release-cleanup

name	post-release-cleanup
description	Merges a released release/* branch back into main or support/17.x, tags the merge commit, creates the GitHub Release, bumps version.json for next-cycle nightlies, and deletes the release branch. Use after the release build is green AND the package has been manually pushed to MyGet.
allowed-tools	Bash, Read, Edit, AskUserQuestion

Post-Release Cleanup (satellite)

Run this after the release branch's CI build is green and the package has been manually pushed to MyGet. This is the point where a version is actually shipped — nothing in git or CI observes the manual MyGet push directly, so tagging and creating the GitHub Release happen here, not on branch push or CI completion.

Workflow

1. Confirm the release actually shipped. Ask the user (AskUserQuestion) to confirm the package for this release branch was pushed to MyGet. If not confirmed, stop — do not tag or merge an unpublished release.

2. Identify the release branch and its target:

   • release/* branches cut from main merge back into main (v18)
   • release/* branches cut from support/17.x merge back into support/17.x (v17)

   If ambiguous, ask the user.

3. Fetch latest state:

   git fetch origin --tags
   

4. Merge the release branch into its target:

   git checkout main                  
   git pull origin main                
   git merge --no-ff origin/release/<name> -m