Skip to content

Add security label to triage workflow and release notes#3516

Merged
jlowin merged 1 commit intomainfrom
add-security-label-and-release-section
Mar 15, 2026
Merged

Add security label to triage workflow and release notes#3516
jlowin merged 1 commit intomainfrom
add-security-label-and-release-section

Conversation

@jlowin
Copy link
Copy Markdown
Member

@jlowin jlowin commented Mar 15, 2026

After a wave of security-related PRs (SSRF, path traversal, auth bypass, scope escalation), we had no way to distinguish them from ordinary bug fixes in triage or release notes.

This adds a security label to the Marvin triage workflow with guidance that draws a clear line between exploitable vulnerabilities and regular auth/correctness bugs — the key question being "could a malicious actor exploit this?" rather than "does this break for legitimate users."

The release notes template gets a new Security 🔒 section (after Enhancements, before Fixes), with exclusion rules so security PRs don't also appear under Fixes, Enhancements, or Dependencies. Also moves Breaking Changes up to second position (after Features) and freshens up a couple emoji choices.

@jlowin jlowin added the enhancement Improvement to existing functionality. For issues and smaller PR improvements. label Mar 15, 2026
@jlowin jlowin merged commit b5a4503 into main Mar 15, 2026
8 checks passed
@jlowin jlowin deleted the add-security-label-and-release-section branch March 15, 2026 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Improvement to existing functionality. For issues and smaller PR improvements.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant