Revert NuGet 7.6 release notes change (awaiting correct file location)

[Copilot]

Based on feedback, the NuGet 7.6 release notes change was reverted. The intended update — documenting that dotnet nuget verify now outputs CRL and OCSP URLs for certificates (NuGet.Client #7181) — should instead be made to docs/core/tools/dotnet-nuget-verify.md, which lives in the dotnet/docs repository rather than this one.

Changes

• docs/release-notes/NuGet-7.6.md — Reverted the previously added "Summary: What's New in 7.6" section; no net changes to this file.

Note: The actual documentation update for CRL/OCSP URL verbosity output in dotnet nuget verify needs to be made in the dotnet/docs repository at docs/core/tools/dotnet-nuget-verify.md.

[learn-build-service-prod]

Learn Build status updates of commit 3fb5c04:

⚠️ Validation status: warnings

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-service-prod]

Learn Build status updates of commit 1b74ccf:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/release-notes/NuGet-7.6.md	✅Succeeded	View

For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[jeffkl]

@copilot do not update the release notes, instead update docs/core/tools/dotnet-nuget-verify.md with my original instructions

[Copilot]

@copilot do not update the release notes, instead update docs/core/tools/dotnet-nuget-verify.md with my original instructions

I've reverted the NuGet 7.6 release notes change (f1bc446). However, docs/core/tools/dotnet-nuget-verify.md doesn't exist in this repository — the dotnet nuget verify CLI reference is maintained in the dotnet/docs repository at docs/core/tools/dotnet-nuget-verify.md. Could you clarify — should this PR be redirected to that repository instead?

[learn-build-service-prod]

Learn Build status updates of commit f1bc446:

⚠️ Validation status: warnings

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.

[jeffkl]

@copilot do not update the release notes, instead update docs/core/tools/dotnet-nuget-verify.md with my original instructions

I've reverted the NuGet 7.6 release notes change (f1bc446). However, docs/core/tools/dotnet-nuget-verify.md doesn't exist in this repository — the dotnet nuget verify CLI reference is maintained in the dotnet/docs repository at docs/core/tools/dotnet-nuget-verify.md. Could you clarify — should this PR be redirected to that repository instead?

@copilot yes, create the PR in dotnet/docs instead. thanks

[Copilot]

@jeffkl I've opened a new pull request, #3566, to work on those changes. Once the pull request is ready, I'll request review from you.