| name | release-rsdoctor |
| description | Use when asked to release Rsdoctor packages for a specific version. All `@rsdoctor/*` packages (except `@rsdoctor/mcp-server`) are versioned together via changesets. |
Release Rsdoctor
Input
- Target version, for example
1.5.8
If the version is missing, ask for it before making changes.
Steps
-
Check the worktree with git status --short. If there are uncommitted edits, stop and ask the user how to proceed.
-
Create and switch to branch release_v<version> (underscore, not slash). If the branch already exists, stop and ask the user how to proceed.
-
Run changesets to bump changed packages:
pnpm changeset version
All @rsdoctor/* packages (except @rsdoctor/mcp-server) move together as a fixed group — see .changeset/config.json.
-
Review the diff. Confirm version bumps are correct across packages and pnpm-lock.yaml is updated.
-
Commit with this exact message: release: v<version>
-
Push the branch, then create a GitHub PR with gh pr create. Use the same text for the PR title: release: v<version>
-
If .github/PULL_REQUEST_TEMPLATE.md exists, keep its structure.
Fill it with:
Summary: Release @rsdoctor/* packages v<version>.Related Links: https://github.com/web-infra-dev/rsdoctor/releases/tag/v<version>
-
After the PR is created, a maintainer will run the release GitHub Action to publish to npm, then merge the PR to main.
