Release

---
name: release
description: Prepare captain-miao release notes or workspace version bumps, and cut, publish or recover releases.
---

# Releasing captain-miao

Match the requested scope:

- **Changelog only:** use [changelog guidance](references/changelog.md). Finish
  the requested entry without changing versions or creating a release tag.
- **Version bump only:** update the version sources below and verify the lock
  with `cargo check --workspace --locked`. Commit under the repository's
  working rules; a version bump alone does not request a tag or publication.
- **Prepare or cut a release:** use [release preparation](references/release.md#prepare-the-release)
  and the changelog guidance. Complete the notes, version bump and checks before
  presenting the release for review.
- **Publish or recover a release:** use the applicable
  [publication or recovery section](references/release.md#publish) and establish
  the current tag, workflow and registry state before acting.

Follow [AGENTS.md](../../../AGENTS.md) for checks, concurrent committers and
path-scoped commits. Reuse authorization already given in the conversation;
release-note review and pushing are governed by the release reference.

## Version sources

`Cargo.toml`'s `[workspace.package] version` is authoritative. Refresh
`Cargo.lock` with `cargo check --workspace` after a bump, then inspect the diff
for the inheriting workspace members' versions and any unrelated changes.
CI builds with `--locked`, so the lock belongs in the same commit.

The npm versions and launcher dependency pins are generated by
`scripts/stage-npm-packages.sh` from the Cargo version. Leave their source
manifests alone when bumping a release. Tag the version-bump commit, never its
parent: release CI checks the tagged tree's version and changelog together.