Clarify package pruning in project files documentation#3532
Conversation
Added clarification on package pruning and its relation to shared frameworks.
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit c4036e2:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/consume-packages/Package-References-in-Project-Files.md | View | Details |
docs/consume-packages/Package-References-in-Project-Files.md
- Line 501, Column 117: [Warning: file-not-found - See documentation]
Invalid file link: '../reference/nuspec'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
There was a problem hiding this comment.
Pull request overview
This PR updates the PrunePackageReference documentation to clarify how the SDK’s predefined pruning list is derived, especially in relation to shared frameworks and framework references.
Changes:
- Clarifies that the predefined pruning list is based on shared frameworks specified in the project.
- Notes that only direct framework references are considered, and framework references introduced via packages don’t contribute pruning data.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 86ba79e: ✅ Validation status: passed
For more details, please refer to the build report. |
Fixes: NuGet/Home#14747
Added clarification on package pruning and its relation to shared frameworks.