Add emergency yank process for unsafe threat detection releases#32
Open
Add emergency yank process for unsafe threat detection releases#32
Conversation
4 tasks
Agent-Logs-Url: https://github.com/github/gh-aw-threat-detection/sessions/12f810e1-d6c2-4df2-b9f0-09cae2d660ce Co-authored-by: davidslater <12449447+davidslater@users.noreply.github.com>
Agent-Logs-Url: https://github.com/github/gh-aw-threat-detection/sessions/12f810e1-d6c2-4df2-b9f0-09cae2d660ce Co-authored-by: davidslater <12449447+davidslater@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add an emergency yank process for unsafe threat detection releases
Add emergency yank process for unsafe threat detection releases
May 7, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds an “emergency yank” capability to the threat-detection release lifecycle so maintainers can mark unsafe releases as yanked, keep audit artifacts, prevent latest from resolving to unsafe versions, and document/validate the lifecycle metadata that gh-aw must consult before execution.
Changes:
- Introduces a lifecycle registry (
releases/threat-detection-lifecycle.json) plus Go-based validation tests for lifecycle/yank metadata correctness. - Adds a manual Yank Release workflow to mark a release as yanked, retag
latestto a safe replacement, and update GitHub Release metadata accordingly. - Updates spec/docs and the promote workflow to incorporate lifecycle-state checks and document yank semantics.
Show a summary per file
| File | Description |
|---|---|
| specs/threat-detection-spec.md | Adds lifecycle/yank requirements to the threat detection spec and renumbers security requirements. |
| releases/threat-detection-lifecycle.json | Adds initial lifecycle registry file (schema v1) to be consumed by gh-aw and maintainer workflows. |
| releases/lifecycle_test.go | Adds validation logic/tests for registry schema, yanked metadata requirements, and replacement constraints. |
| README.md | Documents release lifecycle concepts and the emergency yank behavior at a high level. |
| Makefile | Adds validate-lifecycle target to run lifecycle registry validation tests. |
| DEVGUIDE.md | Documents lifecycle registry expectations and a step-by-step emergency yank process for maintainers. |
| .github/workflows/yank-release.yml | Adds a manual workflow to perform the yank: validate tags/digests, update registry, retag latest, and update GitHub Releases. |
| .github/workflows/promote-release.yml | Blocks promotion of yanked/obsolete releases to latest based on the lifecycle registry. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 8/8 changed files
- Comments generated: 2
Agent-Logs-Url: https://github.com/github/gh-aw-threat-detection/sessions/85fb37b4-0ed2-455c-9ca1-a156a74d65bb Co-authored-by: davidslater <12449447+davidslater@users.noreply.github.com>
Collaborator
|
@copilot resolve the merge conflicts in this pull request |
Agent-Logs-Url: https://github.com/github/gh-aw-threat-detection/sessions/827177cf-9662-48f1-8ea5-bffe053ed198 Co-authored-by: davidslater <12449447+davidslater@users.noreply.github.com>
Co-authored-by: davidslater <12449447+davidslater@users.noreply.github.com>
Agent-Logs-Url: https://github.com/github/gh-aw-threat-detection/sessions/827177cf-9662-48f1-8ea5-bffe053ed198 Co-authored-by: davidslater <12449447+davidslater@users.noreply.github.com>
Contributor
Author
Resolved the merge conflicts with |
Agent-Logs-Url: https://github.com/github/gh-aw-threat-detection/sessions/d9664543-c97b-4b2a-a73c-25db1a57db4d Co-authored-by: davidslater <12449447+davidslater@users.noreply.github.com>
|
|
||
| validate_tag() { | ||
| local tag="$1" | ||
| if ! echo "$tag" | grep -Eq '^v[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.-]+)?(\+[0-9A-Za-z.-]+)?$'; then |
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.
Uh oh!
There was an error while loading. Please reload this page.