release

Release

Prepare a versioned release or Claude Code marketplace catalog state tag: analyze commits, update release files, create a release commit, tag locally, and optionally publish a GitHub Release.

Options

The user may provide these options inline:

• --major: Force a major version bump regardless of commit analysis
• --minor: Force a minor version bump regardless of commit analysis
• --patch: Force a patch version bump regardless of commit analysis
• --dry-run: Preview all changes without modifying any files, committing, or tagging

Workflow

1. Pre-Flight Checks

Run these commands in parallel to understand the current state:

# Check for uncommitted changes
git status --porcelain

# Get current branch name
git branch --show-current

# List existing version tags, sorted by version
git tag --list 'v*' --sort=-version:refname

# List existing Claude Code marketplace catalog state tags
git tag --list 'catalog-M*-m*-p*-n*' --sort=-creatordate

# Get today's date
date +%Y-%m-%d

# Check for a release workflow that publishes GitHub Releases automatically
if [ -d .github/workflows ]; then
  for f in .github/workflows/*.yml .github/workflows/*.yaml; do
    [ -f "$f" ] || continue
    # Tag-triggered workflows: a `tags:` trigger plus a list entry like
    # `- "v*"` or `- catalog-*`.
    has_tag_trigger=0
    if grep -q 'tags:' "$f" && grep -qE "^[[:space:]]*-[[:space:]]+['\"]?(v[*[0-9]|catalog-)" "$f"; then
      has_tag_trigger=1
    fi
    # Marketplace push-to-main automation: workflow invokes the canonical
    # catalog state computation, publishes a GitHub Release, AND triggers
    # on push to the default branch (main or master). All three are
    # required. The compute-catalog-state and gh release create checks
    # rule out partial automation (e.g., a validation workflow that
    # computes the catalog state without tagging or releasing). The push
    # trigger check rules out workflow_dispatch-only or PR-only workflows
    # that happen to mention both strings: those will not run when a
    # commit lands on main, so deferring to them would silently skip
    # local catalog tagging and leave nothing tagged or released. The
    # branches:/main match must occur *under* push: rather than under a
    # sibling key like pull_request: -- otherwise a workflow with
    # `pull_request: branches: [main]` would falsely match. The awk
    # script tracks indentation to scope branches: matches to the push:
    # block, and handles both inline (`branches: [main]`) and YAML-list
    # (`branches:` followed by `- main`) forms.
    has_marketplace_push_to_main=0
    if grep -q 'compute-catalog-state' "$f" && grep -q 'gh release create' "$f" && awk '
        function leading_ws(s) {
          match(s, /^[[:space:]]*/)
          return RLENGTH
        }
        {
          # When indentation falls back to the push: level (or shallower),
          # we have left the push: block. Reset state before running other
          # rules on this line so a sibling key (e.g. pull_request:) does
          # not pick up branches: matches inside push:.
          if (in_push && $0 !~ /^[[:space:]]*$/ && leading_ws($0) <= push_indent) {
            in_push = 0
            in_list = 0
          }
        }
        /^[[:space:]]*push:[[:space:]]*$/ {
          push_indent = leading_ws($0)
          in_push = 1
          in_list = 0
          next
        }
        # Inline form: branches: [main], branches: ["main", "master"],
        # branches: [dev, main]. Strip brackets and quotes, split on
        # commas/whitespace, then compare each token. This avoids needing
        # word-boundary support, which BSD awk lacks ([maintenance] and
        # [main_v2] do not produce a "main" or "master" token).
        in_push && match($0, /branches:[[:space:]]*\[[^]]*\]/) {
          s = substr($0, RSTART, RLENGTH)
          gsub(/\[/, "", s)
          gsub(/\]/, "", s)
          gsub(/"/, "", s)
          gsub(/\047/, "", s)
          n = split(s, a, /[, ]+/)
          for (i = 1; i <= n; i++) {
            if (a[i] == "main" || a[i] == "master") {
              found = 1
              break
            }
          }
        }
        # YAML-list form: a `branches:` line followed by indented
        # `- main` / `- master` entries. Exact line anchors avoid needing
        # word-boundary support.
        in_push && /^[[:space:]]+branches:[[:space:]]*$/ {
          in_list = 1
          next
        }
        in_list && /^[[:space:]]+-[[:space:]]+["'\''"]?(main|master)["'\''"]?[[:space:]]*$/ {
          found = 1
          in_list = 0
        }
        in_list && !/^[[:space:]]+-/ && !/^[[:space:]]*$/ { in_list = 0 }
        END { exit !found }
      ' "$f"; then
      has_marketplace_push_to_main=1
    fi

    # Push-to-main automation is more specific than a generic tag trigger.
    # If a workflow matches both, classify it as push-to-main so marketplace
    # catalog tags remain workflow-owned.
    if [ "${has_marketplace_push_to_main}" -eq 1 ]; then
      printf '%s\t%s\n' "$f" "marketplace-push-to-main"
    elif [ "${has_tag_trigger}" -eq 1 ]; then
      printf '%s\t%s\n' "$f" "tag-triggered"
    fi
  done
fi