⚠️ Retired — alpha-only since 2026-07-25

The fleet ships from alpha and nowhere else: no alpha → beta, no beta → main, no stable versions. alpha is the repo's default branch, the plugin marketplace clones it, every documented install reads #alpha, and calver-release.yml now only triggers on alpha — so the pipeline this skill describes has no runway left. See CLAUDE.md → Branch Strategy.

Kept rather than deleted (Nothing is Deleted) in case a beta channel is ever wanted again; if so, re-check every command here against the current maw/CI before trusting it.

/release-beta

Cut a beta pre-release for the current repo.

Beta sits between alpha (bleeding edge) and main (stable): alpha → beta → main

Assumptions

• Repo has scripts/calver.ts that supports --beta + --check
• Repo has a beta branch on origin
• calver-release.yml auto-tags + publishes when a version-bump commit lands on beta
• Current branch is NOT main, alpha, or beta

Step 0: Detect repo + verify state

date "+🕐 %H:%M %Z (%A %d %B %Y)"
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null) || { echo "❌ Not in a git repo"; exit 1; }
BRANCH=$(git -C "$REPO_ROOT" branch --show-current)
echo "📁 $REPO_ROOT"
echo "🌿 $BRANCH"

Hard checks:

[ "$BRANCH" != "main" ] || { echo "❌ On main"; exit 1; }
[ "$BRANCH" != "alpha" ] || { echo "❌ On alpha"; exit 1; }
[ "$BRANCH" != "beta" ] || { echo "❌ On beta"; exit 1; }
[ -z "$(git -C "$REPO_ROOT" status --porcelain)" ] || { echo "❌ Working tree dirty"; exit 1; }
git -C "$REPO_ROOT" fetch origin beta 2>/dev/null