Release notes for NuGet 7.0.1 #3509
Conversation
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 9f4aff9:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/release-notes/NuGet-7.0.1.md | View | Details | |
| docs/release-notes/Index.md | ✅Succeeded | View | |
| docs/TOC.md | ✅Succeeded | View |
docs/release-notes/NuGet-7.0.1.md
- Line 0, Column 0: [Warning: filename-invalid-character - See documentation]
Only lowercase letters, numbers, and hyphens are allowed in filenames. - Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'mruizmares' is not a valid GitHub ID. - Line 0, Column 0: [Suggestion: filename-incomplete - See documentation]
The filename contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
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 adds release notes for NuGet 7.0.1, a patch release following NuGet 7.0. The release notes document a single bug fix related to Central Package Management with floating versions, and updates the documentation index and table of contents to include the new release.
- Added NuGet 7.0.1 release notes documentation
- Updated release notes index and TOC to include NuGet 7.0.1
- Introduced NuGet 7.x section in the TOC hierarchy
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/release-notes/NuGet-7.0.1.md | New release notes file for NuGet 7.0.1, documenting the NU1011 fix for Central Package Management with floating versions |
| docs/release-notes/Index.md | Added NuGet 7.0.1 entry at the top of the release notes index |
| docs/TOC.md | Added NuGet 7.x section header and NuGet 7.0.1 entry to the table of contents structure |
|
|
||
| | NuGet version | Available in Visual Studio version | Available in .NET SDK(s) | | ||
| | :---|:---|:---| | ||
| | [**7.0.1**](https://nuget.org/downloads) | [Visual Studio 2026 version 18.0.0](https://visualstudio.microsoft.com/downloads/) | [10.0.100](https://dotnet.microsoft.com/download/dotnet/10.0)<sup>1</sup> | |
There was a problem hiding this comment.
Should we update dotnet version to 10.0.101
| ms.topic: release-notes | ||
| --- | ||
|
|
||
| # NuGet 7.0.1 Release Notes |
There was a problem hiding this comment.
Should this doc be under 7.0 ?
There was a problem hiding this comment.
Instead of a new doc, we could add this as a section under 7.0
There was a problem hiding this comment.
have a look at other release notes. We always put the new patch at the top of the doc, so that when people open the release notes page, they find the latest patches at the top of the page, they don't need to scroll to the bottom. But yes, this should not be in a new file.
There was a problem hiding this comment.
Instead of a new doc, we could add this as a section under 7.0
That's a good point - I don't see any other patches in the TOC. For example:
For 5.0.2, a section was added to 5.0's release notes:
Summary: What's New in 5.0.2
https://learn.microsoft.com/en-us/nuget/release-notes/nuget-5.0-rtm#summary-whats-new-in-502
|
|
||
| [Known Issues](../release-notes/known-issues.md) | ||
|
|
||
| [NuGet 7.0.1](../release-notes/NuGet-7.0.1.md) |
There was a problem hiding this comment.
Do we add a separate page for patches?
There was a problem hiding this comment.
This is a good catch that was missed when I added 7.0 release notes. The placeholder that was added didn't update the TOC, and neither did the release-notes generator tool. It'd be great to update the tool so that it adds to the TOC as well.
| --- | ||
| title: NuGet 7.0.1 Release Notes | ||
| description: Release notes for NuGet 7.0.1 including new features, bug fixes, and DCRs. | ||
| author: mruizmares |
There was a problem hiding this comment.
There's an error here - needs your GH alias:
Line 4, Column 9: [Warning: author-not-found - See documentation] Invalid value for author: 'mruizmares' is not a valid GitHub ID.
| ms.topic: release-notes | ||
| --- | ||
|
|
||
| # NuGet 7.0.1 Release Notes |
There was a problem hiding this comment.
Instead of a new doc, we could add this as a section under 7.0
That's a good point - I don't see any other patches in the TOC. For example:
For 5.0.2, a section was added to 5.0's release notes:
Summary: What's New in 5.0.2
https://learn.microsoft.com/en-us/nuget/release-notes/nuget-5.0-rtm#summary-whats-new-in-502
|
@donnie-msft @Nigusu-Allehu @jeffkl I have to close this PR, since the branch starts with "release-" its considered production and cannot push new changes. I agree with all the comments and addressed them in the new PR #3510 |
No description provided.