release

Release

Create a versioned GitHub release with automatic version detection, version file updates, tagging, and changelog generation via gh release create --generate-notes.

Arguments

• Version (optional): Explicit version string, e.g., 1.2.0
• --patch / --minor / --major: Semver bump shorthand (overrides auto-detection)
• --dry-run: Preview version bump and changelog without creating anything
• --draft: Create as draft release on GitHub
• --prerelease: Mark as pre-release on GitHub
• --skip-validation: Skip build/test verification before releasing
• --init <commit>: Create initial baseline tag (for first-ever release)

Workflow

1. Check Prerequisites

   • Verify gh CLI is installed and authenticated: gh auth status
   • Verify clean working tree: git status --porcelain
     • If uncommitted changes exist, prompt user to commit or stash first
   • Verify current branch is pushed to remote: git rev-parse --abbrev-ref --symbolic-full-name @{u}

2. Detect Previous Tag

   • Run git describe --tags --abbrev=0 2>/dev/null to find the latest tag
   • If no tags exist:
     • If --init <commit> provided: create baseline tag at specified commit

       git tag v0.0.0 <commit>
       

     • If --init not provided: prompt user with options:
       • Tag current HEAD as v0.0.0 (baseline only, no release)
       • Tag a specific commit as baseline
       • Abort and let user set up tags manually
     • After baseline created, re-run detection

3. Detect Version Files

   Scan project root for known version manifest files. Multiple files may coexist (e.g., Tauri projects have both Cargo.toml and tauri.conf.json).

   Detection File	Version Location	Project Type
   package.json	"version": "X.Y.Z"	Node.js
   Cargo.toml	version = "X.Y.Z"	Rust
   pyproject.toml	version = "X.Y.Z"	Python
   setup.cfg	version = X.Y.Z	Python (legacy)
   tauri.conf.json	"version": "X.Y.Z"	Tauri