Skip to content

docs: record live rollback drill pass in the release ledger - #55

Merged
crypticpy merged 2 commits into
mainfrom
docs/rollback-drill-ledger
Aug 28, 2026
Merged

docs: record live rollback drill pass in the release ledger#55
crypticpy merged 2 commits into
mainfrom
docs/rollback-drill-ledger

Conversation

@crypticpy

@crypticpy crypticpy commented Aug 28, 2026

Copy link
Copy Markdown
Owner

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):

  • RR-H02 — now complete for rc.6 and rc.7: v1.9.0-rc.7 consumed through the live updater (run 33144777338BCHC PR #34, maintainer-merged 929b007), and the live revert/rollback of an update PR is proven under RR-H07. Only the stable-tag run remains.
  • RR-H07 — bad-deploy rollback upgraded from partial to passed: full on-GitHub drill on 2026-08-28 (BCHC PR #35 rollback to rc.6 through required checks + Pages redeploy + live smoke test; BCHC PR #36 roll-forward byte-identical to the maintainer-merged update, git diff 929b007 empty). 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.0 update 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:

  • Update the release-readiness ledger to record the completed rc.7 live updater rehearsal and rollback drill, including the byte-identical roll-forward verification.
  • Align release gates and remaining promotion requirements with the latest rc.7 evidence, while retaining the outstanding stable-tag, content-takedown, credential-response, owner-transfer, and notification work.

Documentation:

  • Record rc.7 consumption, protected-content verification, live rollback evidence, and updated readiness statuses in the canonical release ledger.

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

@sourcery-ai sourcery-ai 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.

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.

@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: 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".

Comment thread docs/release-readiness-status.md
@sourcery-ai

sourcery-ai Bot commented Aug 28, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates 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 drill

sequenceDiagram
    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
Loading

Flow diagram for release-readiness status after the rollback drill

flowchart 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]
Loading

File-Level Changes

Change Details Files
Records rc.7 as complete for the live updater and update-PR rollback requirement.
  • Adds evidence for live consumption of immutable v1.9.0-rc.7 and its maintainer-merged update.
  • Links the live rollback and byte-identical roll-forward drills, while leaving only the stable-tag update run outstanding.
docs/release-readiness-status.md
Upgrades the bad-deploy rollback drill from partial to passed while preserving the remaining drill gaps.
  • Documents the 2026-08-28 rollback to rc.6 through required checks, Pages redeployment, and live smoke testing.
  • Documents the rc.7 roll-forward and verifies it is byte-identical to the maintainer-merged update.
  • Keeps protected-data history purge partial and credential-response/owner-transfer drills open.
docs/release-readiness-status.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

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
@crypticpy
crypticpy merged commit bdf20f2 into main Aug 28, 2026
20 checks passed
@crypticpy
crypticpy deleted the docs/rollback-drill-ledger branch August 28, 2026 18:58
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.

1 participant