Skip to content

Update NuGet Audit pruning feature description #48317

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 10, 2025
Merged

Update NuGet Audit pruning feature description #48317

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bafee38
Update NuGet Audit pruning feature description
nkolev92 Sep 9, 2025
c305f7e
Update docs/core/whats-new/dotnet-10/sdk.md
nkolev92 Sep 10, 2025
f738ad9
Update docs/core/whats-new/dotnet-10/sdk.md
nkolev92 Sep 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/core/whats-new/dotnet-10/sdk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,9 +172,12 @@
## Pruning of framework-provided package references
Starting in .NET 10, the [NuGet Audit](/nuget/concepts/auditing-packages) feature can now [prune framework-provided package references](https://github.com/NuGet/Home/blob/451c27180d14214bca60483caee57f0dc737b8cf/accepted/2024/prune-package-reference.md) that aren't used by the project. This feature is enabled by default for all `net` target frameworks (for example, `net8.0` and `net10.0`) and .NET Standard 2.0 and greater target frameworks. This change helps reduce the number of packages that are restored and analyzed during the build process, which can lead to faster build times and reduced disk space usage. It also can lead to a reduction in false positives from NuGet Audit and other dependency-scanning mechanisms.
Starting in .NET 10, the [NuGet Audit](/nuget/concepts/auditing-packages) feature can now [prune framework-provided package references](/nuget/consume-packages/package-references-in-project-files#prunepackagereference) that aren't used by the project.

Check failure on line 175 in docs/core/whats-new/dotnet-10/sdk.md

View workflow job for this annotation

GitHub Actions / lint

Trailing spaces 

docs/core/whats-new/dotnet-10/sdk.md:175:252 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] https://github.com/DavidAnson/markdownlint/blob/v0.38.0/doc/md009.md
This feature is enabled by default for all frameworks of a project that targets >= .NET 10.0 in the latest SDK.
This change helps reduce the number of packages that are restored and analyzed during the build process, which can lead to faster build times and reduced disk space usage. It also can lead to a reduction in false positives from NuGet Audit and other dependency-scanning mechanisms.
When this feature is enabled, you might see a reduction in the contents of your applications' generated *.deps.json* files. Any package references supplied by the .NET runtime are automatically removed from the generated dependency file.
When a direct package reference is within the pruning range, [`PrivateAssets="all"` and `IncludeAssets="none"` will be applied](/nuget/consume-packages/package-references-in-project-files#how-prunepackagereference-works).
While this feature is enabled by default for the listed TFMs, you can disable it by setting the `RestoreEnablePackagePruning` property to `false` in your project file or *Directory.Build.props* file.
Expand Down
Loading