Skip to content

docs(release): prepare release process - #7

Merged
paul-cch merged 1 commit into
mainfrom
codex/prepare-release-readiness
Jul 15, 2026
Merged

docs(release): prepare release process#7
paul-cch merged 1 commit into
mainfrom
codex/prepare-release-readiness

Conversation

@paul-cch

Copy link
Copy Markdown
Owner

Summary

  • Replace the mixed Unreleased changelog with the notable changes made after v1.0.0.
  • Add a source-only GitHub Release checklist with explicit version and candidate placeholders.
  • Record release gates, exact-head proof, archive verification, abort rules, and clean closeout without creating a versioned section or release object.

Why

The existing Unreleased section still contained entries that were already present when v1.0.0 was 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

  • Changelog boundary check against v1.0.0 and the full tag-to-head commit and file diff.
  • Release checklist Bash blocks parsed with bash -n.
  • Fresh Python 3.11 environment, dependency resolution, and pip check.
  • Ruff, Ruby YAML parsing, and actionlint.
  • Full Python suite, 73 tests.
  • CLI flow suite, 8 tests.
  • Repository Bash syntax and ShellCheck command sets.
  • Quartz import and display detection on macOS.
  • Both Swift tools compiled and completed runtime startup smokes.
  • Installer deployed into a temporary home with launchctl replaced by a no-op shim.
  • Structured autoreview found no accepted or actionable findings.

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.

Copilot AI review requested due to automatic review settings July 15, 2026 17:29

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@paul-cch
paul-cch merged commit cb29a11 into main Jul 15, 2026
7 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread RELEASING.md
RELEASE_NOTES_FILE='<REVIEWED_RELEASE_NOTES_FILE>'

test "$(git rev-parse HEAD)" = "$CANDIDATE_SHA"
test "$(git rev-parse origin/main)" = "$CANDIDATE_SHA"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

@paul-cch

Copy link
Copy Markdown
Owner Author

Landed as cb29a11889185b777b0028eedc7d2da40142e4f7 from reviewed commit 24b9b653c55f835b1ddea82cce559cbef111a867.

Release-boundary proof:

Local validation:

  • Fresh Python 3.11 environment resolved Pillow 12.3.0 and PyObjC Quartz 12.2.1; pip check passed.
  • Changelog boundary and local release-document reference checks passed.
  • Release-document Bash blocks passed bash -n.
  • Ruby YAML parsing and actionlint passed.
  • Ruff passed.
  • Full test suite passed, 73 tests.
  • CLI flow suite passed, 8 tests.
  • Repository Bash syntax and ShellCheck command sets passed.
  • Quartz import and display detection passed on macOS.
  • Both Swift tools compiled and passed runtime startup smokes.
  • The installer deployed into a temporary home with launchctl replaced by a no-op shim, so no live launchd state changed.

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 actions/checkout v7 and actions/setup-python v6 commits. The reviewed Pillow advisory set has no newer entry requiring a higher floor.

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.

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.

2 participants