[release/10.0] Fix NU1903 suppression: use NoWarn instead of WarningsNotAsErrors#66467
Merged
wtgodbe merged 1 commit intorelease/10.0from Apr 24, 2026
Merged
Conversation
WarningsNotAsErrors does not prevent NuGet restore from promoting audit warnings to errors — NuGet has its own WarningsAsErrors mechanism. Switch to NoWarn which suppresses the warning at all stages including restore. This fixes the internal pipeline which has been 100% broken for 48+ hours despite the previous fix in #66423. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
Bot
added
the
needs-area-label
wtgodbe
added
the
tell-mode
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
1 participant
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.
Backport of #66466 to release/10.0
/cc @wtgodbe
Fix NU1903 suppression: use NoWarn instead of WarningsNotAsErrors
Summary of the changes (Less than 80 chars)
Description
{Detail}
Fixes #{bug number} (in this specific format)
Customer Impact
{Justification}
Regression?
[If yes, specify the version the behavior has regressed from]
Risk
[Justify the selection above]
Verification
Packaging changes reviewed?
When servicing release/2.3