pypi-release

Topics in the source

• pypi-release
• When to load
• Step 1 — Pre-flight
• Step 2 — Clean build and check
• Step 3 — Rehearse on TestPyPI
• Step 4 — Tag, publish, verify

Takes a Python package from a clean working tree to a published PyPI release: pre-flight, build, check, rehearse, tag, upload, verify. CANARY: pypi-release-loaded-2026-06-04-ea39c2b5-820c8d070baea5a5 Load when a package is being published to PyPI or TestPyPI. Pre-merge production sign-off (compatibility, observability, rollback) belongs to the ship skill; the two compose. Load automated release when the project should publish from CI on a version bump instead of by hand (setting up or fixing a release.yml, trusted publishing, an approval gate) — it holds the workflow, the owner's one-time setup, and when to prefer it over this runbook. From the project root: Resolve every mismatch first: versionconsistent: false means pyproject.toml and version disagree (dynamic = ["version"] with hatch-vcs removes the second string); tagmatchesversion: false means the tag does not match the code; dist.stale lists old artifacts. The curl should print 404 — a 200 means the version exists, and PyPI never accepts a re-upload of a name==version, even after a yank, so bump instead. Rendering and metadata problems only show after upload, and a real upload spends the version, so rehearse first: The extra

This is an excerpt. Refer to the complete source and its current requirements.