mdvs: Skill for Claude Code

Release Process

Releases go through a branch + PR (because main is protected), then a tag push triggers the GitHub Actions release workflow (cargo-dist) that builds cross-platform binaries and creates a GitHub Release.

Prerequisites

Before releasing, verify:

1. All tests pass:

cargo test --features testing-mocks
cargo clippy --all-targets --features testing-mocks -- -D warnings
just fmt-check

1. Main branch is clean and up to date:

git checkout main && git pull
git status  # must be clean
git log --oneline -5  # review recent commits

1. CI is green on the latest commit:

gh run list --limit 1

Making a release

Step 1: Create release branch

git checkout -b release/v<version> main

Step 2: Bump version and changelog

Use cog bump with --skip-push (since we can't push directly to main):

cog bump --<level> --skip-push    # or --auto --skip-push

This will:

1. Bump the version in Cargo.toml
2. Generate/update CHANGELOG.md from conventional commits
3. Create a bump commit
4. Create a git tag v<new_version>

If cog bump doesn't support --skip-push, do it manually:

1. Edit Cargo.toml version field
2. Run cog changelog > CHANGELOG.md (or update manually)
3. Commit: git commit -am "chore(release): v<version>"

Step 3: Push branch and create PR

git push -u origin release/v<version>
gh pr create --title "chore(release): v<version>" --body "Version bump and changelog for v<version>"

Wait for CI to pass, then merge the PR.

Step 4: Tag and push

After the PR is merged, tag main and push the tag:

git checkout main && git pull
git tag v<version>
git push origin v<version>

The tag push triggers .github/workflows/release.yml, which builds binaries for macOS, Linux, and Windows, and creates a GitHub Release.

Release levels

Level	Example	Use case
--patch	0.1.0 → 0.1.1	Bug fixes
--minor	0.1.0 → 0.2.0	New features
--major	0.1.0 → 1.0.0	Breaking changes
--minor --pre rc	0.1.0 → 0.2.0-rc.1	Release candidate
--auto	(auto-detected)	Let commits decide