Umbraco.Automate: Skill for Claude Code

Post-Release Cleanup

You are the orchestrator for post-release cleanup in the Umbraco.Automate repository.

Task

After a release has been deployed and tagged by the release pipeline, merge the release/hotfix branch back into main and dev, bump version.json on dev so nightly builds produce versions higher than the released version, and optionally clean up the branch.

Why This Matters

Without the version bump on dev, NBGV + Umbraco.GitVersioning.Extensions produces packages like 1.5.0--preview.4.gabcdef0 which sorts lower than the stable 1.5.0 in SemVer — making nightlies useless for testing.

Workflow

Phase 1: Detect Release Context

1. Check current branch — verify it is vN/release/* or vN/hotfix/*:

   git branch --show-current
   

   If not on a release/hotfix branch, ask the user to specify which branch to process.

   Extract the version prefix from the branch — every long-term branch is version-prefixed:

   # e.g. v18/release/2026.06.5 → prefix=v18, major=18
   #      v17/hotfix/2026.06.1  → prefix=v17, major=17
   release_branch=$(git branch --show-current)
   prefix=$(echo "$release_branch" | grep -oE '^v[0-9]+')
   major=$(echo "$prefix" | grep -oE '[0-9]+')
   

   If the branch does not start with vN/, ask the user which version line to target.

2. Fetch latest tags and remote state:

   git fetch origin --tags
   

3. Find product version tags on this branch that are not yet on main:

   # Get the merge-base between the release branch and this line's main
   merge_base=$(git merge-base origin/$prefix/main HEAD)
   
   # Get all commits on the release branch since the merge-base
   commits=$(git rev-list $merge_base..HEAD)
   
   # For each product tag matching *@*, check if it points at one of these commits
   for tag in $(git tag --list '*@*'); do
       tag_commit=$(git rev-parse "$tag^{commit}" 2>/dev/null)
       if echo "$commits" | grep -q "$tag_commit"; then
           echo "$tag"
       fi
   done