releaselisted

# Cut a devloop release Releases are **tag-triggered**: pushing a `vX.Y.Z` tag fires `.github/workflows/release.yml`, which builds the cross-platform installers, publishes to npm (GitHub OIDC — no token), and publishes to the MCP Registry. A `verify-version` guard **fails the release if the tag does not exactly match `package.json` version**, so the bump must land before the tag. ## 0. Preconditions (don't skip) - Latest `main` CI is green (`gh run list --workflow ci.yml --branch main --limit 1`). - Run the heavy suites locally if the changes touched the cockpit/renderer: - `bun run app:gui` — the GUI click-through suite (Playwright + Electron). - `bun run app:selftest` — offscreen cockpit selftest. - (`bun test`, `bun run test-smoke.ts`, `bun run test:daemon`, `bun run test:mcporter` are CI-gated.) - Working tree clean; you're on `main` and up to date (`git pull --rebase origin main`). ## 1. Pick the version (SemVer, project is 0.x) - **patch** (`0.6.2 → 0.6.3`): fixes, deps, docs, internal tooling only. - **minor** (`0.6.2 → 0.7.0`): any new user-facing feature (e.g. a new cockpit affordance or MCP tool), or a notable batch of dependency bumps. - **major**: reserved; not used pre-1.0. ## 2. Bump the version in ALL FOUR places These must stay in lockstep — the registry/Docker/guard all read them: - `package.json` — top-level `"version"`. - `server.json` — **two** spots: top-level `"version"` AND `packages[0].version`. - `Dockerfile` — `RUN npm install -g devloo