Release

You are assisting with creating a new release by pushing a semver tag and publishing a GitHub release.

1. Preflight Check

Verify the current branch is the default branch:

git rev-parse --abbrev-ref HEAD

If the current branch is not main or master, stop immediately and tell the user which branch they are on. Do not proceed with any release steps.

2. Current Version

Get the latest semver tag:

git tag --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -1

If no tags exist, treat the current version as v0.1.0, proceed to step 3 using all commits, then skip to step 4.

3. Changes Since Last Release

List commits with full messages since the latest tag (or all commits if no tags exist):

# If a tag exists:
git log <latest-tag>..HEAD --format="%h %s%n%b"

# If no tags exist:
git log HEAD --format="%h %s%n%b"

Read the commit subjects and bodies to understand the nature of each change. Display a brief summary of what changed.

4. Version Bump Determination

Assess the overall impact of the changes:

• Breaking changes (API incompatibility, removed endpoints, renamed fields) → major
• New features or capabilities added → minor
• Bug fixes, performance improvements, internal refactoring, dependency updates → patch

State your recommendation with reasoning.

Then ask the user to confirm or override via AskUserQuestion:

Which version bump type?
- patch: vX.Y.Z → vX.Y.(Z+1)
- minor: vX.Y.Z → vX.(Y+1).0
- major: vX.Y.Z → v(X+1).0.0

5. Push Tag

Compute the next version from the bump type. Display: <current-tag> → <next-tag>

Ask the user to confirm via AskUserQuestion before proceeding.

On confirmation:

git tag <next-tag>
git push origin <next-tag>

Show workflow runs triggered by the tag push:

gh run list --branch <next-tag>

6. Create Draft GitHub Release

Create a draft release using GitHub's auto-generated release notes:

gh release create <next-tag> \
  --draft \
  --generate-notes \
  --title "<next-tag>"

Display the draft release URL.

7. Publish Release

Ask the user to confirm publishing via AskUserQuestion.

On confirmation:

gh release edit <next-tag> --draft=false

8. Final Output

• Pushed tag: <next-tag>
• GitHub Actions: show run URL from gh run list --branch <next-tag> --limit 1 --json url --template '{{range .}}{{.url}}{{end}}'
• GitHub release: show URL from gh release view <next-tag> --json url -q .url