Repository navigation
feat(skills): add release-captain skill for the weekly release cadence - #4435
Draft
matthewgrossman wants to merge 1 commit into
Draft
matthewgrossman wants to merge 1 commit into
matthewgrossman wants to merge 1 commit into
Conversation
Add an internal skill with Monday pre-flight, Tuesday stable cut, and recovery steps for the RFC 0014 release train. All tag, workflow, merge, and Slack actions require explicit maintainer approval. Closes #4433 Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
This branch has not been deployed
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
Add an internal
release-captainskill with a checklist for the weekly RFC 0014 release train: Monday pre-flight, the Tuesday stable cut, and recovery. Every action that changes something (tags, workflow runs, merges, Slack/GitHub posts) requires explicit maintainer approval.Related Issue
Closes #4433
Changes
.agents/skills/release-captain/SKILL.md:Release Tag; check publication; seed the next train's-pre.1on a later commit with green CI, then dispatch it.Release Taghas no concurrency guard), and never repoint a stable tag.CONTRIBUTING.mdskills table and thesync-agent-inframaintenance map.This complements #4335 (
release-openshell) and changes no workflows. If #4335 lands, the skill's note that pushing a-pre.*tag doesn't startRelease Tagneeds a one-line update. If #4419 renames qualification jobs or artifacts, the commands will need the same update.Testing
markdownlint-cli2passes onCONTRIBUTING.md. The repo's markdownlint config excludes.agents/**, so the skill file wasn't linted.v0.1.4-pre.3→ run 38248106021), downloading the latest attempt's qualification and compatibility artifacts,jqfield extraction (current_profile_passed,review.verdict), the pre-tag checks (tested onv0.1.4-pre.3as the candidate; the stable-tag check fires on thev0.1.3commit), and the job-failure filter on thev0.1.3release run 37947117841.Checklist