erupt: Command for Claude Code

erupt release SOP

Release version: $ARGUMENTS (call it VER below).

If no version was given above, read it from <version> in erupt/pom.xml and ask the user to confirm.

Publishing to Maven Central is done by the user, not by this command.

Repos are siblings under ~/Code:

Repo	Branches	What happens
erupt	develop → master	merge, tag VER with the changelog
erupt-web	develop → master	merge, tag VER with the changelog
erupt-cube	main	tag VER
erupt-flow	main	tag VER
erupt-tenant	master	tag VER

Step 1 — merge and tag

1.1 Preflight (read-only, stop on any red check)

• gh auth status succeeds.
• Every repo above has a clean working tree, is on the branch in the table and is level with its remote after git fetch. Untracked .flattened-pom.xml files do not count.
• Tag VER exists neither locally nor on origin (git ls-remote --tags origin VER) in any repo.
• erupt-cube, erupt-flow and erupt-tenant already depend on erupt VER in their pom.xml, and each has commits since its previous tag (git log --oneline $(git describe --tags --abbrev=0)..HEAD).
• ~/Code/erupt-docs/en/guide/changelog.md has a ## VER ( section. Read the local file as it is; do not pull or edit erupt-docs. If the section is missing, stop and ask the user.

1.2 Extract the changelog

Take the section from ## VER ( up to the next ## <digit> heading, turn the docs-relative links into absolute ones, and put the version line on top:

DOCS=~/Code/erupt-docs/en/guide/changelog.md
NOTES=<scratchpad>/release-notes-$VER.md
awk -v v="$VER" 'index($0, "## " v " (") == 1 {f = 1; print "erupt " substr($0, 4); next}
                 f && /^## [0-9]/ {exit} f' "$DOCS" \
  | sed -E 's#<Badge [^>]*text="([^"]*)"[^>]*/>#(\1)#; s#\]\(/(en|zh)/#](https://docs.erupt.xyz/\1/#g' > "$NOTES"

Show the user the first lines of $NOTES and its line count.

1.3 Merge develop → master (erupt, erupt-web)