docs(release): prepare release process - #7
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 24b9b653c5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| RELEASE_NOTES_FILE='<REVIEWED_RELEASE_NOTES_FILE>' | ||
|
|
||
| test "$(git rev-parse HEAD)" = "$CANDIDATE_SHA" | ||
| test "$(git rev-parse origin/main)" = "$CANDIDATE_SHA" |
There was a problem hiding this comment.
Refresh origin/main before tagging
In this release flow the only fetch happens back in the Prepare section before the CI/dependency/live-host proof, so if another commit lands on main during that interval, this check still compares against the stale local tracking ref and can allow tagging/publishing <CANDIDATE_SHA> after the real remote branch has moved. Refresh the remote state in the create gate, or compare against git ls-remote, before pushing the tag.
Useful? React with 👍 / 👎.
|
Landed as Release-boundary proof:
Local validation:
Review and CI:
Live-proof boundary: this PR changes repository documentation and release metadata only. It does not alter product behavior or a live host path, so built, source, installer, and workflow proof is the applicable boundary. Dependency refresh: Pillow 12.3.0 and PyObjC Quartz 12.2.1 remain the current stable resolutions. The workflow pins the current stable Privacy Gate: PASS. Public Model Identifier Gate: PASS. The exact diff, PR body, CI logs, proof text, and tracked artifacts contained no blocking private data, identifiers, or unknown generated artifacts. GitHub-hosted runner home paths in CI logs were classified as public runner metadata. |
Summary
v1.0.0.Why
The existing Unreleased section still contained entries that were already present when
v1.0.0was tagged. Publishing that boundary later would repeat old work and obscure the actual tag-to-head changes.WalBridge also had no repository-local release procedure. The new checklist documents the current source distribution model and keeps future release work behind explicit owner authorization.
Validation
v1.0.0and the full tag-to-head commit and file diff.bash -n.pip check.launchctlreplaced by a no-op shim.Boundary
This PR changes documentation and release metadata only. It does not add a versioned changelog section, change a version source, create a tag or GitHub Release, publish a package, deploy Pages, or change the live host. No external live boundary applies to the changed files.
Privacy Gate: PASS. Public Model Identifier Gate: PASS.