Skip to content
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

Create NuGet 6.1 release notes #2667

Merged
merged 11 commits into from
Feb 18, 2022
1 change: 1 addition & 0 deletions docs/TOC.md
Original file line number Diff line number Diff line change
Expand Up @@ -307,6 +307,7 @@
### [Known Issues](release-notes/known-issues.md)

### NuGet 6.x
#### [NuGet 6.1](release-notes/NuGet-6.1.md)
#### [NuGet 6.0](release-notes/NuGet-6.0.md)
### NuGet 5.x
#### [NuGet 5.11](release-notes/NuGet-5.11.md)
Expand Down
2 changes: 2 additions & 0 deletions docs/release-notes/Index.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ ms.topic: conceptual

[Known Issues](../release-notes/known-issues.md)

[NuGet 6.1](../release-notes/NuGet-6.1.md)

[NuGet 6.0](../release-notes/NuGet-6.0.md)

[NuGet 5.11](../release-notes/NuGet-5.11.md)
Expand Down
120 changes: 120 additions & 0 deletions docs/release-notes/NuGet-6.1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,120 @@
---
title: NuGet 6.1 Release Notes
description: Release notes for NuGet 6.1 including new features, bug fixes, and DCRs.
author: zivkan
ms.author: zivkan
ms.date: 2/15/2022
ms.topic: conceptual
---

# NuGet 6.1 Release Notes

NuGet distribution vehicles:

| NuGet version | Available in Visual Studio version | Available in .NET SDK(s) |
|:---|:---|:---|
| [**6.1.0**](https://nuget.org/downloads) | [Visual Studio 2022 version 17.1](https://visualstudio.microsoft.com/downloads/) | [6.0.200](https://dotnet.microsoft.com/download/dotnet-core/6.0)<sup>1</sup> |

<sup>1</sup> Installed with Visual Studio 2022 with.NET Core workload

## Summary: What's New in 6.1

* Show help only for the error itself has to do with a command, argument, or option being invalid with `dotnet nuget` command - [#10788](https://github.com/NuGet/Home/issues/10788)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we please update the issue title and the release notes so that we show what's the new behavior in the release rather than the problem? For example, 10788 would be better described as: "show subcommand help instead of main dotnet nuget trust command help for all cases."

We are already doing the above for 11091, so we only need to address this one.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aortiz-msft - I addressed your comment. Please review whenever you have a minute so that I can merge this PR ASAP.


* Sort the package vulnerabilities in descending order in PMUI details pane - [#11091](https://github.com/NuGet/Home/issues/11091)

### Issues fixed in this release

**DCRs:**

* Disable nuget.exe pack for project.json by default, add a fallback env var to enable it - [#11214](https://github.com/NuGet/Home/issues/11214)

* [DCR]: Adjust compatibility rules for Apple TFMs in .NET - [#11338](https://github.com/NuGet/Home/issues/11338)

* [DCR][No Customer Impact]: NuGetPackage (VS extension entry point) should not use DTEEvents - [#11360](https://github.com/NuGet/Home/issues/11360)

* [DCR]: Improve NuGet.Client build and debugging speed by making ilmerge targets use MSBuild up to date checks - [#11386](https://github.com/NuGet/Home/issues/11386)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is engineering right? Probably the tool should skip it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Created NuGet/Entropy#66 to address this comment.


* [DCR]: Mitigate missing nuget.org when non-NuGet tool creates nuget.config without any sources - [#11387](https://github.com/NuGet/Home/issues/11387)

* [DCR]: NuGet.VisualStudio and NuGet.VisualStudio.Contracts to follow Visual Studio version numbers - [#11394](https://github.com/NuGet/Home/issues/11394)

* [DCR]: Deprecate VS Extensibility APIs that use System.Version - [#11412](https://github.com/NuGet/Home/issues/11412)

* [DCR]: Obsolete VS extensibility APIs that use System.Runtime.Versioning.FrameworkName - [#11419](https://github.com/NuGet/Home/issues/11419)

* Remove Mac Catalyst warning - [#11438](https://github.com/NuGet/Home/issues/11438)

**Bugs:**

* Confusing restore output: it did some restore on one of the projects, but at the end it still prints "All packages are already installed and there is nothing to restore" - [#4376](https://github.com/NuGet/Home/issues/4376)

* dotnet nuget push - Missing value for option - [#4864](https://github.com/NuGet/Home/issues/4864)

* Restore does not print enough info in the output when fails - [#6047](https://github.com/NuGet/Home/issues/6047)

* Minimal VS install has broken NuGet UI - [#8414](https://github.com/NuGet/Home/issues/8414)

* Visual Studio hangs at "Clear All NuGet cache(s) - [#9831](https://github.com/NuGet/Home/issues/9831)

* Versions List in Details Pane is not kept in sync when changing Selected Package - [#10557](https://github.com/NuGet/Home/issues/10557)

* File Conflict dialog does not have access keys - [#10691](https://github.com/NuGet/Home/issues/10691)

* ContentItemCollection uses yield return which is causing over-allocation of Enumerators - [#10921](https://github.com/NuGet/Home/issues/10921)

* UIDelay: `nuget.packagemanagement.visualstudio.dll!NuGet.PackageManagement.VisualStudio.VsCoreProjectSystemReferenceReader+<GetProjectReferencesAsync>d__` - managed projects - [#11163](https://github.com/NuGet/Home/issues/11163)

* [Bug]: MSBuild restore is logging exception as warning - [#11179](https://github.com/NuGet/Home/issues/11179)

* [Bug]: String comparison approach used for Source and Namespaces is not consistent - [#11182](https://github.com/NuGet/Home/issues/11182)

* There is no tooltip for the “install” button on the right of a package in "Browse" tab - [#11189](https://github.com/NuGet/Home/issues/11189)

* Async Service Provider should be invoked on threadpool threads via the built in TService,TInterface extensions instead of custom casting - [#11200](https://github.com/NuGet/Home/issues/11200)

* [Bug]: VS crashes when package sources dropdown in PM UI has multiple package sources whose names are equal when compared using Culture Ignore Case - [#11241](https://github.com/NuGet/Home/issues/11241)

* The strings "ms" and "sec" are not localized on Output - Package Manager window. - [#11297](https://github.com/NuGet/Home/issues/11297)

* Sort Package Source dropdown list using locale/culture setttings in PM UI - [#11298](https://github.com/NuGet/Home/issues/11298)

* Update SDPX license list from da7ecca to fafa781 - [#11309](https://github.com/NuGet/Home/issues/11309)

* [Bug]: NuGet.Localization isn't generated - [#11328](https://github.com/NuGet/Home/issues/11328)

* [Bug]: assembly-loading MEF composition in NuGet.Tools VS package's synchronous event handlers can cause responsiveness delays - [#11334](https://github.com/NuGet/Home/issues/11334)

* [Bug]: NuGet SDK resolver should not throw if project path is NULL - [#11376](https://github.com/NuGet/Home/issues/11376)

* [Bug]: PackageSourceMapping inconsistencies should be reported - [#11385](https://github.com/NuGet/Home/issues/11385)

* [Bug]: `RegistryKeyUtility.GetValueFromRegistryKey()` has unused parameter, leading to incorrect results - [#11407](https://github.com/NuGet/Home/issues/11407)

* Reduce heap allocations in ResolverUtility.FindLibraryByVersionAsync - [#11409](https://github.com/NuGet/Home/issues/11409)

* [Bug]: Package Source Mapping matches found should not be logged for projects - [#11413](https://github.com/NuGet/Home/issues/11413)

* [Bug]: Avoid explicitly casting the result of GetService/GetServiceAsync, use the extension methods instead - [#11451](https://github.com/NuGet/Home/issues/11451)

* [Bug]: Package Source options in VS does not announce package sources or checkbox status - [#11482](https://github.com/NuGet/Home/issues/11482)

* [Bug]: VS package source options clears all checkboxes when adding or removing sources - [#11521](https://github.com/NuGet/Home/issues/11521)

**StillOpens:**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these are meant to be removed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed this section in the latest commit.


* Remove project.json pack - [#7931](https://github.com/NuGet/Home/issues/7931)

* Async implementation of IVS Package Installer/Uninstaller services - [#8896](https://github.com/NuGet/Home/issues/8896)

**Nones:**

* NuGet no longer uses CPS's JTF - [#8317](https://github.com/NuGet/Home/issues/8317)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These probably need to have a type added.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am considering removing this * NuGet no longer uses CPS's JTF - [#8317](https://github.com/NuGet/Home/issues/8317) from the release notes because the linked PR fixes NuGet/Home#8414 bug which is already added to the bugs list.


* [5.x] Make restore types that are project.json-specific obsolete - [#9149](https://github.com/NuGet/Home/issues/9149)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is that making type obsolete falls under Type:Engineering work. Hence removing this from the release notes.


* [Bug]: Use IAsyncServiceProvider extension methods instead of type casting ourselves - [#11339](https://github.com/NuGet/Home/issues/11339)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing this issue from the release notes because the issue has Type:Engineering label.


* Remove NUGET_FRAMEWORKS_INTERNAL compiler constant - [#11418](https://github.com/NuGet/Home/issues/11418)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing this issue from the release notes because the issue has Type:Engineering label.


**[List of all issues fixed in this release - 6.1](https://app.zenhub.com/workspaces/nuget-client-team-55aec9a240305cf007585881/reports/release?release=Z2lkOi8vcmFwdG9yL1JlbGVhc2UvNjY5ODY)**