Skip to content

docs(security): Release path & compromise scope appendix (#219) - #297

Open
Chris-Wolfgang wants to merge 1 commit into
vNextfrom
docs/219-security-appendix
Open

docs(security): Release path & compromise scope appendix (#219)#297
Chris-Wolfgang wants to merge 1 commit into
vNextfrom
docs/219-security-appendix

Conversation

@Chris-Wolfgang

Copy link
Copy Markdown
Owner

Appends the "Release path & compromise scope" section to SECURITY.md — the load-bearing per-repo facts a maintainer would need if the release identity is compromised. Matches the canonical shape from Etl-DbClient #240; generic incident-response steps are intentionally not duplicated.

All five bullets filled in for this repo:

  • Release path — OIDC / Trusted Publishing via NuGet/login@v1, no long-lived key
  • Fallback — none; OIDC identity Chris-Wolfgang/console-app-template
  • Owner@Chris-Wolfgang
  • Downstream consumers — none internal (it's a dotnet new template pack, not a code dependency)
  • Package coordinates — the four published package IDs with nuget.org links

Docs-only; no version bump, no template-content change (won't affect generated projects or the snapshot).

Closes #219

🤖 Generated with Claude Code

Append the "Release path & compromise scope" section to SECURITY.md with this
repo's specific facts: OIDC/Trusted-Publishing release path (NuGet/login@v1, no
long-lived key), no fallback (OIDC identity Chris-Wolfgang/console-app-template),
owner, downstream-consumer note (template pack, no internal code dependents), and
the four package coordinates for unlisting. Docs-only; matches the canonical shape
from Etl-DbClient #240.

Closes #219

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 15, 2026 19:26

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants