-
Notifications
You must be signed in to change notification settings - Fork 498
Add documentation for NU1016 error code (project.json deprecation) #3469
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.
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
base: main
Are you sure you want to change the base?
Conversation
Learn Build status updates of commit 40d5b6b: ✅ Validation status: passedFor more details, please refer to the build report. |
Co-authored-by: nkolev92 <[email protected]>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. 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 5344788: 💡 Validation status: suggestions
docs/reference/errors-and-warnings/NU1016.md
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. |
Learn Build status updates of commit 34c1e37: 💡 Validation status: suggestions
docs/reference/errors-and-warnings/NU1016.md
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. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. 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 |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. 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 4cca413: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds comprehensive documentation for the NU1016 error code, which is raised when NuGet encounters deprecated project.json
projects during restore operations. The error indicates that projects using the deprecated project.json
format need to be migrated to the newer PackageReference format.
- Added complete documentation for NU1016 error following established documentation patterns
- Updated the errors and warnings index to include the new NU1016 entry
- Provided migration guidance with step-by-step instructions for different Visual Studio versions
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
File | Description |
---|---|
docs/reference/errors-and-warnings/NU1016.md | New documentation page explaining NU1016 error with migration guidance |
docs/reference/Errors-and-Warnings.md | Added NU1016 link to the "Invalid input errors" table |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Learn Build status updates of commit e4d2270: ✅ Validation status: passed
For more details, please refer to the build report. |
Fixes https://github.com/nuget/home/issue/14415
This PR adds missing documentation for the NU1016 error code, which is raised when NuGet encounters a deprecated
project.json
project during restore operations.Changes Made
docs/reference/errors-and-warnings/NU1016.md
- Complete documentation for the NU1016 error following the established pattern of other error documentationdocs/reference/Errors-and-Warnings.md
- Added NU1016 to the "Invalid input errors" table