ops-release

# OPS ► RELEASE — one-command plugin publish Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). Cuts a new published version of the **claude-ops** plugin: bumps the version in the three manifests, writes the CHANGELOG, opens a release PR, waits for CI, merges it to `main`, and pushes the `vX.Y.Z` tag. After it runs, `/ops:ops-update` pulls the new version down to the box. > **`ops-release` ships it · `/ops:ops-update` pulls it.** Order: merge your fix PR > → `/ops:ops-release` → `/ops:ops-update`. ## ⚠️ Run it from the REPO CHECKOUT, not the cache `bin/ops-release` resolves its targets **relative to its own location**: `PLUGIN_DIR = <bin>/..`, `REPO_ROOT = <bin>/../..`, and it needs `REPO_ROOT/.claude-plugin/marketplace.json`. The plugin **cache** (`~/.claude/plugins/cache/ops-marketplace/ops/<ver>/bin/ops-release`) has **no** `marketplace.json` above it, so running the cache copy fails with `not found: …/.claude-plugin/marketplace.json`. Always run the copy inside a **git checkout** of the repo (the dir that has both `.claude-plugin/marketplace.json` and `claude-ops/bin/ops-release`). Resolve it first: ```bash RELEASE="" for d in ~/Developer/repos/claude-ops ~/Projects/claude-ops-workspace/claude-ops ~/Projects/claude-ops/claude-ops "$HOME"/Projects/*/claude-ops; d...