docs: record live rollback drill pass in the release ledger - #55
Conversation
The live revert-PR rollback leg deferred to the rc.7 window has now run: BCHC PR #35 rolled the deployment back to v1.9.0-rc.6 through required checks, Pages redeploy and live verification, and BCHC PR #36 rolled forward to v1.9.0-rc.7 byte-identical to the maintainer-merged update. RR-H02 also records the rc.7 update consumption (run 33144777338, BCHC PR #34); only the stable-tag run remains. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD
There was a problem hiding this comment.
Sorry @crypticpy, you've used your own review budget of 250,000 diff characters for the last 7 days.
You can request another review in 12 hours and 33 minutes by commenting @sourcery-ai review. Upgrade to get a review now.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8d7708c950
ℹ️ 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".
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates the canonical release-readiness ledger to align with the BCHC drill inventory: rc.7 live consumption and update rollback are now evidenced, and the bad-deploy rollback drill is marked passed, while the stable-tag run and unrelated operational drills remain outstanding. Sequence diagram for the live release rollback drillsequenceDiagram
participant PHCT as PHCT release
participant Updater as BCHC live updater
participant PR34 as BCHC PR 34
participant PR35 as BCHC PR 35
participant Pages as Pages deployment
participant PR36 as BCHC PR 36
PHCT->>Updater: Consume v1.9.0-rc.7
Updater->>PR34: Create update pull request
PR34-->>Updater: Merge update at 929b007
PHCT->>PR35: Roll back bad deployment to v1.9.0-rc.6
PR35->>Pages: Required checks and redeploy
Pages-->>PR35: Live smoke test passes
PHCT->>PR36: Roll forward to v1.9.0-rc.7
PR36-->>PHCT: git diff 929b007 is empty
Flow diagram for release-readiness status after the rollback drillflowchart LR
RC6[v1.9.0-rc.6 consumed] --> RC7[v1.9.0-rc.7 consumed]
RC7 --> Rollback[Bad-deploy rollback passed]
Rollback --> Stable[Stable-tag update run remains]
Rollback --> Open[Credential-response and owner-transfer drills remain open]
Rollback --> Partial[Protected-data history purge remains partial]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
The overview, the exact-update-rehearsal row and the protected-content row still described the rc.7 candidate and updater pass as outstanding after the RR-H02/RR-H07 rows recorded them complete. Record the rc.7 cut (PR #54, b97432b), the live updater consumption (run 33144777338, BCHC PR #34, 929b007) and the rollback drill in all three places so only the stable-tag work remains listed as open. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD
Updates the canonical release ledger (
docs/release-readiness-status.md) so it no longer contradicts the BCHC drill inventory (raised by review on BCHC PR #37):v1.9.0-rc.7consumed through the live updater (run 33144777338 → BCHC PR #34, maintainer-merged929b007), and the live revert/rollback of an update PR is proven under RR-H07. Only the stable-tag run remains.git diff 929b007empty). Content takedown stays partial (protected-data history purge unrehearsed); credential-response and owner-transfer stay open.BCHC's copy of this ledger syncs at the next template update (the stable
v1.9.0update PR). Docs-only change.🤖 Generated with Claude Code
https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD
Summary by Sourcery
Record the successful rc.7 live update and rollback evidence in the release-readiness ledger and update the remaining release requirements.
Enhancements:
Documentation: