Release qualification workflow: tickets per surface on a release candidate, and the gate - #14
Merged
Merged
Conversation
…idate, and the gate A pull request that changes the package version (or carries the release label) gets one issue per required runtime surface with no decision for that version, carrying the checklist and the commands; the merge is gated on every required surface having a record or a waiver and on the README's runtime table being current. The runs happen on maintainers' machines and accounts; nothing secret is held here. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DVKYxSeRJWncZVsmaxC4p4 Signed-off-by: Claude <noreply@anthropic.com>
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.
Pull request
What and why
The release-candidate workflow of the maintainer-run qualification process, so a copy of the template inherits it (ADR B; the release qualification guide in the marketplace repository). On a pull request that changes the package version, or carries the
releaselabel, build-kit'srelease_tickets.pyopens one issue per required runtime surface with no decision for that version, carrying the checklist verbatim, the commands to record a run or waive the surface, and the runtime maintainer team; it closes the issue when the record or waiver lands on the branch and keeps one comment on the pull request with the state per surface. Thenosp.py advertise --check --release --into README.mdgates the merge. Only the workflow's own token is used. On an ordinary pull request the workflow says so and passes.Checklist
git commit -s)commands/directories anywhere (everything is a skill)~/.netrccontents anywhere in the diffReviews
Ordinary gate change; one maintainer review.
🤖 Generated with Claude Code
https://claude.ai/code/session_01DVKYxSeRJWncZVsmaxC4p4
Generated by Claude Code