Skip to content

skill: add release-manager (release channels, RC flow, audit gates)#667

Open
xdotli wants to merge 1 commit into
mainfrom
skill/release-manager
Open

skill: add release-manager (release channels, RC flow, audit gates)#667
xdotli wants to merge 1 commit into
mainfrom
skill/release-manager

Conversation

@xdotli

@xdotli xdotli commented Jun 11, 2026

Copy link
Copy Markdown
Member

A reusable release-management skill capturing what the current cycle exercised, so future releases are managed consistently. Complements launch-prep.

Encodes the two things the automation enforces that surprise people:

  1. any v* tag publishes to public PyPI (incl. v…rc1), and
  2. public-release is main-gated (a tag must be on main or the workflow hard-fails).

Plus: the three channels (public / internal-preview / release-candidate), the RC-without-merging-to-main flow (non-v* tag + GitHub prerelease wheel — exactly what 0.6.0-rc.1 did), the CITATION.cff/FORCE_COLOR checklist gotchas, and the pre-tag audit gates including independent cross-model review.

Dev tooling under .claude/skills/ — not shipped in the wheel (sdist allowlist excludes it), safe to merge to main independently.


Note

Low Risk
Documentation-only under .claude/skills/; no runtime, CI, or packaging behavior changes.

Overview
Adds a new user-invocable Claude skill release-manager under .claude/skills/ that documents how BenchFlow releases are supposed to work end-to-end.

It encodes automation gotchas (any v* tag hits public PyPI; public-release requires the tag on main), maps the three channels (public, internal .devN preview, RC), and gives runbooks: public cut (wraps launch-prep), RC testing via non-v* tags + GitHub prerelease wheels without merging to main, plus pre-tag audit gates (CITATION.cff, FORCE_COLOR, CI/e2e/adversarial review). Dev-only docs—not shipped in the wheel.

Reviewed by Cursor Bugbot for commit 1ba8fc9. Bugbot is set up for automated code reviews on this repo. Configure here.

Captures the release machinery's two gotchas (any v* tag publishes to
PyPI; public-release is main-gated), the three channels (public /
internal-preview / release-candidate), the RC-without-merging-to-main
flow via a non-v* tag + GitHub prerelease wheel, and the pre-tag audit
gates incl. independent cross-model review. Complements launch-prep.
Dev tooling under .claude/ (not shipped in the wheel).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant