Skip to content

CI: Keep NuGet vulnerability findings non-blocking - #241

Open
Charles Gagnon (Charles-Gagnon) wants to merge 1 commit into
mainfrom
dev/chgagnon/fix-pr-nuget-audit
Open

Charles Gagnon (Charles-Gagnon) wants to merge 1 commit into
mainfrom
dev/chgagnon/fix-pr-nuget-audit

Conversation

@Charles-Gagnon

@Charles-Gagnon Charles Gagnon (Charles-Gagnon) commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator

Keep NuGet package vulnerability findings (NU1901-NU1904) visible as warnings without blocking GitHub PR validation. This prevents vulnerabilities from blocking PRs that are unrelated to the packages themselves - we track these vulnerabilities through other means.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@ch0707

Copy link
Copy Markdown
Contributor

this PR summary has internal ado stuff that needs to be cleaned up and not relevant

env:
DOTNET_ROLL_FORWARD: LatestMajor
# NuGet package vulnerability errors should not block PR validation.
WarningsNotAsErrors: NU1901;NU1902;NU1903;NU1904

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.

can we limit this to low and moderate findings?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather not - since any of those will currently block the PR build from completing due to us surfacing all warnings as errors.

As mentioned in the description - we track these vulnerabilities in other ways so having this PR pipeline fail for any of them is just noise and very unlikely to catch "real" issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants