onde-cli: Skill for Claude Code

Release skill

End-to-end release procedure for onde-cli. Complements the git skill (merge rules) and the distribution skill (channel details) — this skill is the concrete runbook.

Decide the version

• Look at git tag -l 'v*' --sort=-v:refname | head -1 for the latest release.
• Look at the commits since (git log v<latest>..development --oneline). Fixes and chores only → patch bump. New user-facing features → minor bump.
• Check for an abandoned release/vX.Y.Z branch — its version is usually the intended next one. If it exists, inspect it (git log development..release/...) before deciding to reuse or delete it; do not blindly branch -D without looking, and never reuse a branch whose commits were made unsigned or by the wrong identity.

Version bump surfaces

These files pin the crate version and must all move together:

• Cargo.toml — version = "X.Y.Z" in [package]
• pub/onde_cli/pubspec.yaml — version: X.Y.Z
• server.json — three occurrences: top-level version, and the npm and NuGet packages[].version entries (search for the old version string to catch all)

docs/mcp-registry.md and .github/workflows/release-mcp-registry.yml mention past versions only as historical examples — do not bump those.

The npm wrapper manifests are NOT bump targets: the committed package.json files are rewritten at release time by npm/scripts/render-*.cjs from the tag.

After editing, run cargo check --locked (or let the build update Cargo.lock) so the lockfile carries the new version, and commit it in the same bump commit.

Sequence

Follow the git skill's branch flow — release/vX.Y.Z → development → main, --no-ff at every hop, tag on the final main merge commit. Concretely:

git checkout development
git pull <remote> development          # start from the pushed tip
git checkout -b release/vX.Y.Z
# ... edit the bump surfaces ...
git commit -am "Prepare vX.Y.Z"        # signed, correct identity (see below)
git checkout development
git merge --no-ff release/vX.Y.Z -m "Merge release prep for vX.Y.Z"
git checkout main
git pull <remote> main
git merge --no-ff development -m "Merge development for vX.Y.Z"
git tag vX.Y.Z
git push <remote> development main vX.Y.Z
git branch -d release/vX.Y.Z           # only after the merge lands