release

# Cut a release The release workflow (`.github/workflows/release.yml`) is triggered by a `v*` tag and its **first step is a hard version-match guard**: if the tag doesn't match the version in both source-of-truth files, the whole release (GitHub release + GHCR image + MCP registry publish) fails. This skill makes the two files agree *before* the tag is pushed. > The advertised MCP `Implementation` version is **not** a third file to bump: it is > build-derived from `gradle.properties` (`server/build.gradle.kts` bakes `project.version` > into a resource read by `ServerVersion`) and asserted by `ServerVersionTest`, so it can > never drift and needs no separate guard. ## 1. Determine the new version Use `$ARGUMENTS` if given. Otherwise read the current version from `gradle.properties` (`version=`), decide the bump with the user (semver), and confirm. Call the new value `<VERSION>` (no `v` prefix inside files; the git tag is `v<VERSION>`). ## 2. Bump the version in BOTH guarded files The tag guard checks these exact patterns (keep the formatting identical): 1. `gradle.properties` — the line `version=<VERSION>` (guard: `^version=<VERSION>$`). This is the single source of truth; the runtime MCP version is derived from it (see the note above), so there is no third file to bump. 2. `server.json` — the top-level `"version": "<VERSION>"` (guard: `jq .version == <VERSION>`). Note: the workflow later also rewrites `server.json` `.version` and `.packages[0].identifier` f...