You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/updating-packages.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,3 +35,10 @@ Any assembly listed in the `.vsixignore` file certainly follows the above advice
35
35
For packages that are only referenced by `src/NuGet.Clients/` projects, it's safe to update as soon as VS's main branch has the updated package/assembly version.
36
36
In that case, it's not necessary to wait until the dependency is updated in a public preview, since it won't affect the .NET SDK.
37
37
For packages/assemblies that we include in the vsix (see the `.vsixinclude` file), it's probably safe to update at any time.
38
+
39
+
## Ingesting packages from the dotnet-public mirror
40
+
41
+
The client build uses the dotnet-public mirror for ingesting nuget.org packages.
42
+
The [mirroring packages](https://github.com/dotnet/arcade/blob/main/Documentation/MirroringPackages.md) document has details about how this ingestion happens and when and how to ingest new packages or package versions.
0 commit comments