Repository navigation
docs: Update SECURITY.md re full disclosure of unreleased vulnerabilities - #1217
Conversation
Clarified vulnerability reporting procedures and updated support policy for older versions. Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com>
There was a problem hiding this comment.
Review Summary
This PR makes documentation-only changes to SECURITY.md, reorganizing the policy by merging the "Backporting" section into "Supported Versions" and adding a new paragraph clarifying that prerelease/tip-of-master vulnerabilities should be disclosed publicly via a GitHub issue.
Blocking issue:
The PR title "Update SECURITY.md with reporting and support details" does not conform to the project's required Conventional Commits format. Per the project guidelines, the title must start with a type prefix from the Angular convention. For a documentation change, the correct prefix is docs:.
Suggested title: docs: update SECURITY.md with reporting and support details
The content changes themselves are clear and accurately reflect the described intent (merging the Backports section and clarifying full-disclosure norms for prereleases).
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
Clarifies that full disclosure is the norm for vulnerabilities that haven't reached an official release, and merges the Backports section into the Supported Versions section.
Need help on this PR? Tag
@codesmith-botwith what you need.