publishlisted

# Publish ## CI/CD Pipeline `release.yml` builds release binaries for 3 targets and creates the GitHub Release with binary assets: - `aarch64-apple-darwin` (macOS ARM64) - `x86_64-unknown-linux-gnu` (Linux x86_64) - `aarch64-unknown-linux-gnu` (Linux ARM64) **Flow**: version-bump PR merges to `main` → `release.yml`'s `preflight` job tags the merge commit itself → same run builds the 3 binaries and creates the GitHub Release. There is no separate manual tag step: tagging is part of the automated pipeline, not a step this skill performs. The `v*` tag-push trigger still exists as a manual/emergency escape hatch (see the last section below) but is not part of the normal flow. ## Version Locations Version must be updated in **3 files** (all must match): 1. `Cargo.toml` — `version` field 2. `.claude-plugin/plugin.json` — `version` field 3. `.claude-plugin/marketplace.json` — `version` field inside `plugins[0]` ## Version Bump Workflow ### Step 1: Pre-flight checks ```bash git branch --show-current # Must not be main when files are changed git status # Must be clean git fetch --tags --quiet ``` Show the latest tag and current `Cargo.toml` version. If currently on `main`, create a release preparation branch before changing files. ### Step 2: Ask for the new version Use AskUserQuestion. Show the current version and suggest semver options (patch, minor, major). ### Step 3: Update version 1. Use the Edit tool to update the `version` field in all 3 files