Merge to live - June releases

.github/workflows/stale-issues.yml

@@ -22,13 +22,13 @@ jobs:
       - uses: actions/stale@v9
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
-          stale-issue-message: 'Thanks for sharing your feedback. We apologize for our delayed response. Due to the sheer volume of feedback in our repo, we have decided to prioritize the newest issues and are automatically closing our oldest issues with an Issues bot. If you believe your feedback is still actionable, then either respond directly in this issue or open a new documentation issue and we’ll review. If no activity occurs in the next 14 days, this issue will be closed.'
+          stale-issue-message: 'Thanks for sharing your feedback. We apologize for our delayed response. Throughout 2024 we are phasing out GitHub issues as the feedback mechanism on documentation content and replacing it with a new feedback system. If you believe your feedback needs to be reviewed prior to closing, then respond directly in this issue and we’ll take a look at it. If no activity occurs in the next 7 days, this issue will be closed.'
           close-issue-message: 'This issue is closed. If you feel this issue has been closed in error, please submit a new comment on the issue, and we will review it.'
           stale-issue-label: 'stale'
           close-issue-label: 'auto-close'
           exempt-issue-labels: 'exempt,P1'
           remove-stale-when-updated: true
-          days-before-close: 14
-          days-before-issue-stale: 90
+          days-before-close: 7
+          days-before-issue-stale: 20
           days-before-pr-stale: -1
           operations-per-run: 500

docs/consume-packages/Package-Source-Mapping.md

@@ -150,7 +150,7 @@ This configuration is advantageous if you primarily use packages from say, `nuge
 If your team doesn't use standard prefixes for internal package IDs or vets `nuget.org` packages prior to installation, then making a private source the default will suit your needs better.
 
 > [!Note]
-> When the requested package already exists in the global packages folder, no source look-up will happen and the mappings will be ignored. Consider declaring a [global packages folder for your repo](../reference/nuget-config-file.md#config-section) to gain the full security benefits of this feature. Work to improve the experience with the default global packages folder in planned for a next iteration.
+> When the requested package already exists in the global packages folder, no source look-up will happen and the mappings will be ignored. Consider declaring a [global packages folder for your repo](../reference/nuget-config-file.md#config-section) to gain the full security benefits of this feature. Work to improve the experience with the default global packages folder is planned for a next iteration.
 To learn more about how package installation works, see [the conceptual document.](../concepts/package-installation-process.md)
 
 ### Get started

docs/install-nuget-client-tools.md

@@ -40,7 +40,7 @@ Package Manager Console commands work only within Visual Studio on Windows and d
 
 ## Support policy
 
-The Visual Studio for Windows support policy can be found at [Visual Studio Product Lifecycle and Servicing](https://learn.microsoft.com/visualstudio/productinfo/vs-servicing).
+The Visual Studio for Windows support policy can be found at [Visual Studio Product Lifecycle and Servicing](/visualstudio/productinfo/vs-servicing).
 
 
 The most recent version of NuGet.exe is fully supported and can be relied on for bug fixes, updates, and enhancements.
@@ -105,18 +105,18 @@ The following table compares the available features for the dotnet and `nuget.ex
 
 | Feature | dotnet CLI | nuget CLI (Windows) | nuget CLI (Mono) | Visual Studio (Windows) | Visual Studio for Mac |
 | --- | --- | --- | --- | --- | --- |
-| Search packages | | ✔ | ✔ | ✔ | ✔ |
+| Search packages | ✔ | ✔ | ✔ | ✔ | ✔ |
 | Install/uninstall packages | ✔ | ✔ (1) | ✔ | ✔ | ✔ |
 | Update packages | ✔ | ✔ | | ✔ | ✔ |
 | Restore packages | ✔ | ✔ | ✔ (2) | ✔ | ✔ |
-| Manage package feeds (sources) | | ✔ | ✔ | ✔ | ✔ |
+| Manage package feeds (sources) | ✔ | ✔ | ✔ | ✔ | ✔ |
 | Manage packages on a feed | ✔ | ✔ | ✔ | | |
 | Set API keys for feeds | | ✔ | ✔ | | |
 | Create packages (3) | ✔ | ✔ | ✔ (4) | ✔ | |
 | Publish packages | ✔ | ✔ | ✔ | ✔ |  |
 | Replicate packages | | ✔ | ✔ | | |
 | Manage *global-package* and cache folders | ✔ | ✔ | ✔ | | |
-| Manage NuGet configuration | | ✔ | ✔ | | |
+| Manage NuGet configuration | ✔ | ✔ | ✔ | | |
 
 **Feature notes**
 

docs/nuget-org/nuget-org-faq.yml

@@ -86,6 +86,9 @@ sections:
           > [!Note]
           > These environment variables are available since [.NET CLI](https://learn.microsoft.com/nuget/reference/dotnet-commands) (.NET SDK) 6.0.100, [NuGet CLI](https://learn.microsoft.com/nuget/reference/nuget-exe-cli-reference) 6.0, Visual Studio 2022 version 17.0 and corresponding MSBuild version. See [NuGet Release Notes](https://learn.microsoft.com/nuget/release-notes/).
 
+          > [!Important]
+          > NuGet.org recommends Alpine Linux users to upgrade to Alpine Linux 3.18.0 or newer. These versions support TCP fallback in the DNS resolver. If you use older versions of Alpine Linux that only support DNS over UDP, you may encounter DNS failures when accessing the [V3 API](https://learn.microsoft.com/nuget/nuget-org/overview-nuget-org#api-endpoint-for-nugetorg).
+
           If that version of NuGet client continues to fail, [contact support](https://www.nuget.org/policies/Contact) and provide additional connection troubleshooting information including:
 
           - The package sources you're using

docs/nuget-org/organizations-on-nuget-org.md

@@ -101,4 +101,4 @@ You can delete an organization account by clicking the **Delete** button shown i
 
 ![Deleting an organization](media/org-delete-option.png)
 
-To delete the organizaiton, you must confirm it by clicking the **Delete organization** confirmation button.
+To delete the organization, you must confirm it by clicking the **Delete organization** confirmation button.

docs/reference/errors-and-warnings/NU1105.md

@@ -23,7 +23,7 @@ The project file exists but no restore information was provided for it. Ensure y
 
 From the command line this could mean that the file is corrupt or that the `NuGet.targets` are not imported.
 To import the `NuGet.targets`, usually it's recommended to import the `Microsoft.Common.targets`.
-To restore projects in solution using [.NET Core CLI](../../consume-packages/install-use-packages-dotnet-cli.md) use:
+To restore projects in solution using [.NET CLI](../../consume-packages/install-use-packages-dotnet-cli.md) use:
 ```dotnetcli
 dotnet restore MySolution.sln
 ```

docs/release-notes/Known-Issues.md

@@ -3,7 +3,7 @@ title: Known Issues
 description: Known issues with NuGet including authentication, package installation, and tools.
 author: JonDouglas
 ms.author: jodou
-ms.date: 11/11/2016
+ms.date: 06/06/2024
 ms.topic: conceptual
 ---
 
@@ -14,6 +14,25 @@ These are the most common known issues with NuGet that are repeatedly reported.
 > [!Note]
 > Starting with NuGet 4.0, known issues are a part of the respective release notes.
 
+## NuGet Audit settings may not be applied correctly for projects using packages.config in Visual Studio 17.10
+
+NuGet Audit support was added for packages.config projects starting from NuGet 6.10 and Visual Studio 17.10.
+Information on how to configure NuGet Audit can be found in our docs on [our docs on auditing packages](../concepts/Auditing-Packages.md).
+
+**Problem:**
+
+If two or more projects using packages.config in the solution use the same project name, then NuGet Audit will choose one and use the same NuGet Audit settings for both projects.
+
+The tracking issue to remove this limitation is [available on GitHub](https://github.com/NuGet/Home/issues/13466).
+
+**Workaround:**
+
+If all projects with the same name use the same configuration values, then there will be no functional difference when NuGet restores one project using a different project's configuration.
+
+NuGet.exe does not have this limitation, so you can [download NuGet.exe](../install-nuget-client-tools.md#nugetexe-cli) and run `NuGet.exe restore` on your solution to see if the NuGet Audit warnings are different on the command line to what Visual Studio is reporting.
+
+If it is feasible to rename the projects so they have different project names, then this problem scenario will not be encountered.
+
 ## Authentication issues with NuGet feeds in VSTS with nuget.exe v3.4.3
 
 **Problem:**

docs/release-notes/NuGet-6.10.md

@@ -28,6 +28,21 @@ NuGet distribution vehicles:
 
 * dotnet list package --vulnerable requires constant login to 3rd party nuget feed - [#12456](https://github.com/NuGet/Home/issues/12456)
 
+### 6.10.0 Known issues
+
+NuGet.exe 6.10.0 and Visual Studio 17.10.0 may have failures during NuGet operations for projects using packages.config under the following scenarios:
+
+* Two or more projects in the solution have the same name
+* Two or more projects in the solution use the same packages.config file (the project files exist in the same directory)
+
+These issues have been fixed in NuGet.exe 6.10.1 and Visual Studio 17.10.2.
+
+Public tracking issues and discussions can be found in the following locations:
+
+* [Cannot nuget restore after updating visual studio community to 17.10.0. An item with the same key has already been added.](https://developercommunity.visualstudio.com/t/Cannot-nuget-restore-after-updating-visu/10665602)
+* [Visual Studio and PMC restore/update fails when multiple packages.config projects in the solution share the same name (An item with the same key has already been added)](https://github.com/NuGet/Home/issues/13465)
+* [##[error]The nuget command failed with exit code(1) and error(An item with the same key has already been added.](https://github.com/NuGet/Home/issues/13456)
+
 ### Breaking changes
 
 * Add nullable annotations to NuGet.Configuration - [#13250](https://github.com/NuGet/Home/issues/13250)