Repository navigation
docs(release-runbook): change gears on a release-blocking defect - #863
Merged
Merged
Conversation
Distinguish flakes/infra (file a strand, rerun, carry on) from substantive defects (stop, diagnose including the CI gap, file a self-contained strand, work it via /investigate-beads and a reviewed PR, then resume the release after proving the failed pipeline step passes in a dry run). First case: v0.34.0 / bd-yt3x1gwk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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
2 participants
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.
Adds a triage step to §5 of the release runbook. The v0.34.0 release was the first to hit a substantive defect (bd-yt3x1gwk), so this writes down the process we used there:
/investigate-beadsand a reviewed PR.🤖 Generated with Claude Code