Repository navigation
feat(roadmap): require a security section for sensitive plans - #4082
Merged
dan-petty merged 1 commit intoNov 7, 2026
Merged
Conversation
dan-petty
added
type/feature
Closes #3247 The proposal check now refuses a plan that touches a security trigger and gives no security text. The security triggers are SECURITY.md, pyproject.toml, paths under k8s/, and words such as credential or egress. The plan must answer what crosses a trust boundary, what a person must confirm, and what test fails if the rule breaks. The stage job renders this text as the ## Security section in design.md.
dan-petty
force-pushed
the
feat/3247-require-a-security-section-for-sensitive
branch
from
November 7, 2026 22:14
61f1891 to
d36b0fc
Compare
dan-petty
marked this pull request as ready for review
November 7, 2026 22:22
dan-petty
deleted the
feat/3247-require-a-security-section-for-sensitive
branch
November 7, 2026 22:27
dan-petty
pushed a commit
that referenced
this pull request
Nov 7, 2026
🤖 I have created a release *beep* *boop* --- ## [0.85.0](v0.84.1...v0.85.0) (2026-11-07) ### Features * **roadmap:** require a security section for sensitive plans ([#4082](#4082)) ([257cb46](257cb46)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: dan-petty-release[bot] <346998822+dan-petty-release[bot]@users.noreply.github.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
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.
Issue #3247: security and scope questions are left to the model, so plan reviews and fixes returned findings that needed a person, such as a loosened guard, a stored URL, ambient environment variables and a credential redaction in the wrong layer. A deterministic trigger and a non-blank security section make the plan answer what crosses a trust boundary, what a person must confirm, and what test fails if the rule breaks.
Closes #3247
Change:
openspec/changes/archive/2026-11-07-3247-require-a-security-section-for-sensitive/