docs: add obol stack release train playbook#549
Closed
bussyjd wants to merge 0 commit into
Closed
Conversation
10 tasks
OisinKyne
approved these changes
May 25, 2026
ae25b41 to
e679f59
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
release-train.mdreference to the obol-stack development skill.Why
Recent work repeatedly combined PR range review, architectural correctness checks, fix PRs, bot/security review comments, image pin verification, release template discipline, smoke validation, and scoped cleanup. The existing obol-stack skill covered the individual smoke and QA pieces, but not the orchestration of a full PR/release train.
flowchart LR A["Inventory PRs and checks"] --> B["Architectural review"] B --> C{"Incorrect or risky?"} C -- "yes" --> D["Open fix/<topic> PR"] C -- "no" --> E["Mark ready / merge in order"] D --> F["Parallel targeted validation"] F --> E E --> G["Upgrade running cluster"] G --> H["Release-smoke gate"] H --> I{"Green enough to release?"} I -- "no" --> J["Record blockers"] I -- "yes" --> K["Template-based non-draft RC release"]Validation
git diff --cached --checkpython3 /Users/bussyjd/.codex/skills/.system/skill-creator/scripts/quick_validate.py /Users/bussyjd/.codex/worktrees/a251/obol-stack/.agents/skills/obol-stack-dev