release
Release the Antithesis plugin. Use when the user asks to "release the plugin", "cut a release", "bump the version", or gives a version, like "release plugin 0.2.0".
antithesishq · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add antithesishq/antithesis-plugin --skill release技能说明
name: release description: Release the Antithesis plugin. Use when the user asks to "release the plugin", "cut a release", "bump the version", or gives a version, like "release plugin 0.2.0".
Release the plugin
You drive a release end to end, and watch every step until it finishes:
- Open a pull request, from a
release/vX.Y.Zbranch, that bumps the plugin's version and adds its notes toCHANGELOG.md, and watch its checks. - Wait while the user reviews the PR and merges it.
- Watch the Tag release workflow (
.github/workflows/tag-release.yml). The merge of arelease/branch starts it: it tags the merge commit asvX.Y.Z, and runs the Release workflow (.github/workflows/release.yml) on the tag. - Watch the Release workflow. It verifies the tag, runs every check, and creates the GitHub release with that version's
CHANGELOG.mdsection as its notes.
Only a tag makes a GitHub release. CI never does, whatever version the default branch is at.
Users install the plugin from the default branch, and Claude Code and Codex update it when its version changes. So merging the PR ships the version to every user, and the tag and release record it.
The Release PR workflow (.github/workflows/release-pr.yml) opens a release PR every weekday on its own, when CI passed on the default branch and the plugin changed since the last release. Claude picks the version and writes the notes as "Pick and check the version" and "Write the notes" say, in a job that can't write to the repository. Another job writes them to CHANGELOG.md, sets the version, and opens the PR. Started by hand, it takes an optional version, which may be a release candidate: Claude uses it, and the workflow releases even when nothing changed.
A release is X.Y.Z. A release candidate is X.Y.Z-rc.N, and follows the same steps: its PR bumps the default branch to the candidate, so every user gets it too, and its GitHub release is a pre-release. Below, X.Y.Z stands for the whole version, with its -rc.N for a candidate.
1. Pick and check the version
Get the current version from plugins/antithesis/plugin.json. If the user gave a version, strip any leading v. Otherwise, pick the next one once you've read the changes in "Write the notes": bump the minor version if any change is breaking, and the patch version otherwise. When the user asks for a release candidate, the next one after X.Y.Z-rc.N is X.Y.Z-rc.N+1, and the first is -rc.1 of the version you'd pick. Releasing a candidate's X.Y.Z drops the suffix. Say which you picked and why in the PR, so the user can change it in review.
Before changing anything, check:
- The version is
MAJOR.MINOR.PATCHorMAJOR.MINOR.PATCH-rc.N, and higher than the current version. A candidate is lower than its release:0.1.0-rc.2is above0.1.0-rc.1and0.0.9, and below0.1.0. git tag -l vX.Y.Zandgh release view vX.Y.Zfind nothing.git status --porcelainis empty, and you're on the default branch, up to date with the remote.- No release PR is open:
gh pr list --state open --limit 1000 --json url,headRefName,isCrossRepository --jq '.[] | select((.headRefName | startswith("release/")) and (.isCrossRepository | not)) | .url'prints nothing.
If a check fails, tell the user and stop.
2. Write the notes
Write the notes from what changed, not from PR descriptions. A description can show an approach that changed in review, and a later PR can change the behavior again.
Find the previous release, skipping candidates: git fetch --tags && git tag -l 'v[0-9]*' --sort=-v:refname | grep -v -- -rc | head -1. Every candidate's notes, and the release's, cover everything since that release. Read what users get from the plugin since then:
- What the skill tells agents to do:
git diff vPREV..HEAD -- plugins/antithesis/skills/. - How users install it and what it needs:
git diff vPREV..HEAD -- plugins/antithesis/*.json plugins/antithesis/.*-plugin/ .claude-plugin/ .agents/plugins/ README.md docs/.
Then list the commits with git log --oneline vPREV..HEAD. When the diffs don't explain a change, read its commit with git show <sha>. Use the PR number, (#N) at the end of a squash-merged subject, only to link the entry.
If there is no previous release, write a short summary of what the plugin does instead: its modules, and the platforms it installs on.
Write the notes at the level of modules and what the agent does differently:
- One entry per module or feature. Merge the PRs that changed the same thing into one entry.
- Leave out rewording that doesn't change what the agent does, and internal changes: CI, scripts, this skill, contributor docs.
- Write each entry as the net change since the previous release. A module that's new in this release is one entry, not the PRs that built it. When one change reverses another, leave out both.
- Put breaking changes first, then the rest, largest first. A change is breaking if something that worked with the previous release now fails or needs the user to act: a renamed module or command, a new requirement on the user's setup, a changed harness layout that existing workloads need to adopt. Start each with
**Breaking**:and say what to do instead. - Link every PR that contributes to an entry, under the repository's URL from
gh repo view --json url -q .url, e.g.([#7](https://github.com/antithesishq/antithesis-plugin/pull/7)).
Put the notes in CHANGELOG.md under # Version X.Y.Z (YYYY-MM-DD) with today's date, above every other version, and below the HTML comments at the top of the file.
CHANGELOG.md holds at most one candidate's section, at the top. A new candidate replaces the previous candidate's section, heading and notes, with its own. A release replaces it with the release's section. check:changelog fails otherwise. Then check that scripts/changelog-section.py X.Y.Z prints them: the release workflow uses the same script.
3. Bump the version
Run scripts/set-version.py X.Y.Z, th