Skip to content

docs(runbook): R6a precedes R4; D5 lets the testing-tip battery stand in for R6d - #256

Merged
chrisdpurcell merged 1 commit into
testingfrom
runbook-r4
Sep 1, 2026
Merged

chrisdpurcell merged 1 commit into
testingfrom
runbook-r4

Conversation

@chrisdpurcell

Copy link
Copy Markdown
Collaborator

Summary

Two runbook corrections learned on the v5.29.0 train: R4 (make release-reconcile) must run after R6a rebuilds the wheel runtime, because reconcile takes the release it writes from the runtime on PYTHONPATH — on the pre-bump runtime it rendered .standards/catalog.toml at 5.28.0 and the rerun refused with PC-RELEASE-LEVEL (recovered with the documented restore-then-reconcile). And under D5, R6d is satisfied by the integrated --full battery on the testing tip when the release commit touches only R2–R5 paths, so the release commit gets R6c only.

Governing work

Supporting: #236

Acceptance coverage

Verification

prettier and markdownlint on the file.

… in for R6d

The v5.29.0 train ran R4 on the pre-bump runtime and rendered .standards/catalog.toml with the outgoing release, tripping PC-RELEASE-LEVEL on the rerun.
@chrisdpurcell
chrisdpurcell marked this pull request as ready for review September 1, 2026 23:40
@chrisdpurcell
chrisdpurcell merged commit 4ebfcf4 into testing Sep 1, 2026
4 checks passed
@chrisdpurcell
chrisdpurcell deleted the runbook-r4 branch September 1, 2026 23:40
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