release

You are preparing a new release of Stokowski. Follow these steps exactly and interactively — confirm with the user before making any commits or opening PRs.

Step 1: Safety checks

Run the following checks and abort if either fails:

# Check we're on main
BRANCH=$(git branch --show-current)
if [ "$BRANCH" != "main" ]; then
  echo "ERROR: Not on main branch (currently on '$BRANCH'). Switch to main before releasing."
  exit 1
fi

# Check main is up to date with origin
git fetch origin main
LOCAL=$(git rev-parse HEAD)
REMOTE=$(git rev-parse origin/main)
if [ "$LOCAL" != "$REMOTE" ]; then
  echo "ERROR: main is not up to date with origin/main. Pull or push first."
  exit 1
fi
echo "✓ On main and up to date with origin"

If either check fails, stop immediately and tell the user what to fix.

Step 2: Find the baseline

# Get the latest tag, or the first commit if no tags exist
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)
echo "Last release: $LAST_TAG"

Step 3: Collect commits since last release

git log ${LAST_TAG}..HEAD --pretty=format:"%h %s" --no-merges

Review the commits and group them mentally by type:

• feat: — new features (→ minor bump)
• fix: — bug fixes (→ patch bump)
• feat!: or body containing BREAKING CHANGE — breaking changes (→ major bump)
• docs:, chore:, ci:, refactor: — maintenance (→ patch bump if no feat/fix)

Step 4: Propose the semver bump

Get the current version:

grep '^version' pyproject.toml

Apply these rules:

• Any feat!: or BREAKING CHANGE → major bump
• Any feat: (no breaking changes) → minor bump
• Only fix:, chore:, docs:, ci: → patch bump

Tell the user: "Based on the commits, I propose a [major/minor/patch] bump: vX.Y.Z → vA.B.C. Does this look right, or would you like a different version?"

Wait for the user to confirm or specify a different version before continuing.

Step 5: Write the release notes