| name | ce-release-finalize |
| description | Execute the complete calibrated-explanations release handoff: automated preflight, human-gated publication, and automated postcommit cleanup.
|
CE Release Finalize
Finalize a calibrated-explanations release by following release.md exactly.
Load references/pypi_release_guide.md for command details.
Use this skill when
- All implementation tasks for the target version are closed.
- The user asks to release, publish, or ship a version.
- A release needs its final metadata, artifacts, publication, or handoff.
Version contract
- Read the exact PEP 440 release and development versions from the active
version plan. Do not assume the next version is
X.Y.(Z+1) when the master
plan names a minor, major, or prerelease milestone.
make release-preflight updates deterministic release metadata. Do not
duplicate that work manually before the command.- A leading
v is used for tags/citation display, not package/runtime metadata.
Release workflow
Steps 1-10: automated preflight
make release-preflight
make release-finalize
release-preflight owns release-plan readiness, CHANGELOG conversion, all
deterministic release-file updates, tests, notebook execution/save, version
alignment, clean build, Twine/artifact validation, and clean-wheel smoke.
release-finalize verifies that the green snapshot and worktree are unchanged.
For an intentional override:
make release-preflight VERSION=<exact-version> RELEASE_DATE=YYYY-MM-DD
Do not proceed unless both commands exit 0.
Steps 11-13: maintainer only
The maintainer performs and confirms these immutable/external actions:
- Commit, tag, and push.
- Publish/activate/verify the tag on Read the Docs.
- Upload the validated artifacts to TestPyPI/PyPI.
Do not execute these actions. Pause after make release-finalize and wait for
the maintainer to confirm that all three succeeded.
Steps 14-17: automated postcommit
After the maintainer confirms steps 11-13:
make release-postcommit
The command verifies the exact PyPI metadata and rendered page, installs the
published pin in a clean environment with an exact version assertion, uses or
scaffolds the master plan's next milestone, updates release tracking, archives
the released plan, and bumps to the next plan's declared development version.
Use NEXT_VERSION=<milestone> only when the master plan is absent or does not
name the intended transition.
If postcommit creates a scaffold, immediately use ce-release-planner to turn
it into the required content-complete version plan. A scaffold is not release
closure evidence.
Constraints
- Never upload to PyPI, push tags, or publish RTD from this skill; those actions
belong to the maintainer in steps 11-13.
- Never bypass
twine check, preflight, or finalize.
- Steps 11-13 are the only human-gated release actions; do not leave steps
1-10 or 14-17 as undocumented manual follow-ups.
- Follow
release.md and the canonical guide in
references/pypi_release_guide.md.
