draft-release

Draft Release Command

Generate comprehensive GitHub release notes for a given tag, creating a new draft release or updating an existing one.

Arguments

• tag (required): The release tag (e.g., v3.0.0.M1)

Instructions

Execute the following steps to generate and publish draft release notes:

Step 1: Validate Environment

Verify we're in a git repository with a GitHub remote:

# Check we're in a git repo
git rev-parse --git-dir

# Get the GitHub remote URL and extract owner/repo
git remote get-url origin

Extract the repository in owner/repo format from the remote URL. If not a GitHub repository, STOP and inform the user.

Step 2: Validate Tag Exists

# Verify the tag exists
git rev-parse --verify "$TAG" 2>/dev/null

If the tag doesn't exist, STOP and inform the user the tag was not found.

Step 3: Find Previous Tag

# Find the most recent tag before the target tag
git describe --tags --abbrev=0 "$TAG^" 2>/dev/null

# If no previous tag, use the initial commit
git rev-list --max-parents=0 HEAD

Inform the user: Analyzing release $TAG... Previous tag: $PREVIOUS_TAG

Step 4: Get Date Range for PR Query

# Get the date of the previous tag
git log -1 --format=%cI "$PREVIOUS_TAG"

# Get the date of the current tag
git log -1 --format=%cI "$TAG"

Step 5: Fetch Merged PRs

Use the GitHub CLI to fetch all PRs merged between the tags:

gh pr list \
  --repo "$OWNER/$REPO" \
  --state merged \
  --limit 500 \
  --json number,title,author,body,mergedAt,additions,deletions,labels \
  --jq ".[] | select(.mergedAt >= \"$PREV_DATE\" and .mergedAt <= \"$TAG_DATE\")"

Inform the user: Found $COUNT PRs merged between tags

Step 6: Categorize PRs

Analyze each PR and categorize using conventional commit prefixes in the title:

Title Prefix	Category
feat: or feat(	new_features
fix: or fix(	bug_fixes
docs: or docs(	documentation
build: or build( or ci: or ci(	build_ci
test: or test(	test_coverage
refactor: or refactor( or perf: or perf(	build_ci
build(deps): OR author login is dependabot or renovate	dependencies