Skip to content

docs: Update SECURITY.md re full disclosure of unreleased vulnerabilities - #1217

Merged
Pr0methean merged 1 commit into
masterfrom
Pr0methean-patch-4
Oct 29, 2026
Merged

Pr0methean merged 1 commit into
masterfrom
Pr0methean-patch-4

Conversation

@Pr0methean

@Pr0methean Pr0methean commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

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.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

Clarified vulnerability reporting procedures and updated support policy for older versions.

Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com>
@Pr0methean Pr0methean changed the title Update SECURITY.md with reporting and support details docs: Update SECURITY.md re full disclosure of unreleased vulnerabilities Oct 29, 2026

@amazon-q-developer amazon-q-developer Bot 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.

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.

@Pr0methean
Pr0methean enabled auto-merge October 29, 2026 01:23
@Pr0methean
Pr0methean added this pull request to the merge queue Oct 29, 2026
Merged via the queue into master with commit c6ed669 Oct 29, 2026
136 checks passed
@Pr0methean
Pr0methean deleted the Pr0methean-patch-4 branch October 29, 2026 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant