release

Context

• Latest stable: !git tag -l 'v[0-9]*.[0-9]*.[0-9]*' --sort=-v:refname | grep -v '-' | head -1 || echo "none"
• Latest beta: !git tag -l 'v*-beta*' --sort=-v:refname | head -1 || echo "none"
• Current branch: !git branch --show-current
• Git status: !git status --short
• Commits since last tag: !git log $(git describe --tags --abbrev=0 2>/dev/null)..HEAD --oneline 2>/dev/null || git log --oneline -5

Task

Create a new release.

Steps

1. Show current state to the user:

   • Latest stable version
   • Latest beta version (if any)
   • What versions each release type would create

2. Ask user what release to create using AskUserQuestion:

   • Calculate and show concrete version numbers for each option
   • Example options (adjust based on current state):
     • "v0.2.0 (minor)" — requires main branch
     • "v0.1.2 (patch)" — requires main branch
     • "v1.0.0 (major)" — requires main branch
     • "v0.2.0-beta.1 (new beta)" — requires dev branch
     • "v0.2.0-beta.2 (next beta)" — only if beta exists, requires dev branch
   • If argument was provided (e.g., /release patch), skip the question and use it

3. Check prerequisites:

   • Working directory is clean
   • Tests pass: go test ./...
   • IMPORTANT - Branch rules:
     • Stable releases (major/minor/patch): MUST be on main branch
     • Beta releases: MUST be on dev branch
     • If on wrong branch, stop and tell the user to switch branches first

4. Create and push tag:

   VERSION=vX.Y.Z  # or vX.Y.Z-beta.N for beta
   git tag "$VERSION"
   git push origin "$VERSION"
   

5. Monitor release workflow:

   gh run watch --workflow release.yml --interval 10
   

6. Mark as prerelease (beta only):

   gh release edit "$VERSION" --prerelease
   

   This ensures the beta won't be picked up by auto-update (which uses /releases/latest).

7. Verify release:

   gh release view "$VERSION"
   gh release view "$VERSION" --json assets --jq '.assets[].name'