Skip to content

docs: keep 0.5 release tracking state truthful #436

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
codeforester merged 1 commit into from
Oct 8, 2026
Merged

docs: keep 0.5 release tracking state truthful #436

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions docs/release-0.5.0-checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,9 @@

This is release preparation. A dated changelog section does not mean the version
has been tagged or published. The proposed date must be refreshed if publication
happens on another day. Issue #307 remains open until publication evidence exists.
happens on another day. Keep the active 0.5.0 release-tracking issue open until
publication evidence exists; this checklist intentionally does not hard-code a
historical issue number.

1. Merge the reviewed 0.5.0 issue train and all remaining 0.5.0 PRs. Refresh the
release PR against their final integrated commit and include their changelog
Expand All @@ -21,6 +23,13 @@ happens on another day. Issue #307 remains open until publication evidence exist
wheel/sdist, then verify matching SHA256SUMS, SPDX SBOM, provenance and SBOM
attestations, RELEASE-BOM-ROW, tag target, and GitHub release assets.
7. Verify a clean installation of exactly `base-cli==0.5.0` from PyPI. Record the
immutable release URL and evidence on #307, then close it.
immutable tag and GitHub release URLs, PyPI result, checksums, SPDX SBOM,
provenance and SBOM attestations, RELEASE-BOM-ROW, and downstream evidence
on the active release-tracking issue. Close that issue only after every
required artifact and compatibility result has been independently verified.

Merged release preparation is not publication completion: the release is not
complete while the tag, GitHub release, PyPI package, or required evidence is
missing, even when the preparation pull request and local gates are green.

The operational commands and recovery rules remain in [Releasing](releasing.md).
Loading