ci: add cve-fix label and vulnerability category to release notes#253
Merged
WilliamBerryiii merged 3 commits intomainfrom Mar 15, 2026
Merged
ci: add cve-fix label and vulnerability category to release notes#253WilliamBerryiii merged 3 commits intomainfrom
WilliamBerryiii merged 3 commits intomainfrom
Conversation
- add Vulnerabilities Fixed category with cve-fix label - exclude cve-fix from Security category to prevent duplication 🔒 - Generated by Copilot
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the GitHub automatic release notes configuration to surface CVE remediation pull requests in a dedicated “Vulnerabilities Fixed” section and prevent duplication in the existing Security section.
Changes:
- Added a new
🔒 Vulnerabilities Fixedchangelog category keyed off thecve-fixlabel. - Updated the
🔐 Securitychangelog category to exclude PRs labeledcve-fix.
agreaves-ms
reviewed
Mar 14, 2026
agreaves-ms
approved these changes
Mar 14, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repository’s GitHub auto-generated release notes configuration to better surface CVE remediation work by adding a dedicated “Vulnerabilities Fixed” category and preventing duplication within the existing Security category.
Changes:
- Added a new release-notes category 🔒 Vulnerabilities Fixed keyed off the
cve-fixlabel. - Updated the existing 🔐 Security category to exclude PRs labeled
cve-fixto avoid double-listing.
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.
Description
Adds a new 🔒 Vulnerabilities Fixed section to the GitHub automatic release notes configuration and creates the
cve-fixlabel used to categorize CVE-related pull requests. The Security category is updated with an exclusion rule to preventcve-fixPRs from appearing in both sections.Related Issue
Fixes #141
Type of Change
Implementation Details
.github/release.yml: Added🔒 Vulnerabilities Fixedcategory with thecve-fixlabel, positioned between Breaking Changes and Security to surface vulnerability fixes prominently in release notes..github/release.yml: Addedexclude: labels: [cve-fix]to the🔐 Securitycategory to prevent dual-categorization.cve-fixlabel (color#b60205, description "Pull requests that fix CVE vulnerabilities") onmicrosoft/edge-ai.Testing Performed
Validation details: YAML linting passed. Verified release.yml structure and label ordering are correct.
Validation Steps
.github/release.ymland confirm the new🔒 Vulnerabilities Fixedcategory appears with thecve-fixlabel.🔐 Securitycategory has anexcludeblock listingcve-fix.cve-fixlabel exists on the repository with color#b60205.Checklist
terraform fmtandterraform validate(if applicable)bicep formatandbicep build(if applicable)Additional Notes
This is a CI configuration-only change. No infrastructure, application, or documentation changes are included. Most checklist items (Terraform, Bicep, tests, docs) are not applicable.
Screenshots
N/A