Suppress payload pack NU* analysis noise - #8
Merged
Conversation
kzu
enabled auto-merge (rebase)
August 29, 2026 01:14
Member
Author
|
🧪 Details on Ubuntu 24.04.4 LTSfrom retest v1.1.0 on .NET 10.0.11 with 💜 by @devlooped |
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.
Pack analysis treats our Azure CLI Payload like a typical .NET library. CI was logging ~2k warnings that are not actionable:
azps.ps1andActivate.ps1are Payload files, not NuGet install scripts. Azure.Cli already hid this; azx PackAsTool puts the same tree undertools/so it still fired.Moved the shared list (
NU5100;NU5110;NU5111;NU5118;NU5119;NU5123;NU5128;NU5129) intosrc/Directory.propsso both packs inherit it, and dropped the duplicateNoWarnfrom the individual projects.