docs(security): add Release path & compromise scope appendix (#188) - #264
Merged
Conversation
Closes #188. Appends the canonical "Release path & compromise scope" section per the Etl-DbClient #240 template. Fills the 5 bullets with Try-Pattern specifics: - Release path via `NuGet/login@v1` OIDC Trusted Publishing (wired in PR #254; no long-lived API key on the NuGet account). - Fallback: none — OIDC compromise = GitHub-account compromise. - Owner: @Chris-Wolfgang. - Known Wolfgang.* downstream: Wolfgang.D20.Dice. - Package coordinates: Wolfgang.TryPattern on nuget.org. Original scope ("full DISASTER-RECOVERY.md runbook") is superseded by the OIDC decision — the appendix pattern is what stays. Generic incident-response steps (unlisting, advisories, credential rotation) deliberately excluded — GitHub / NuGet own that documentation. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced Jul 28, 2026
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.
Closes #188.
Summary
Appends the canonical Release path & compromise scope section to
SECURITY.md, per the Etl-DbClient #240 template. Fills all 5 bullets with Try-Pattern specifics — OIDC release path, no fallback, owner, downstream consumer (D20-Dice), package coordinates.Original acceptance criteria (full
docs/DISASTER-RECOVERY.mdrunbook) is superseded by the OIDC decision (PR #254); the appendix pattern is what stays. Generic incident-response steps (unlisting, advisories, credential rotation) deliberately excluded — GitHub / NuGet own that documentation and update faster than a checked-in runbook.Stacked-PR base
Base branch is
vNext. First of a new 11-PR batch on vNext.Test plan
SECURITY.mdrenders on GitHub with the appendix[fill in]placeholders left