NuGet Versions and Release History

This section documents MSBuild 18.9, the .NET SDK 10.0.402 (with its dotnet CLI) and NuGet 7.9, as published in the MSBuild, .NET and NuGet documentation on learn.microsoft.com, which is the reference these pages are written and verified against. Material about .NET 11 / NuGet 8.0 is still in preview and is always flagged as such — never presented as baseline.

This content was generated with the assistance of AI and should be verified against the official documentation before being relied on in production.

The C# Reference bibliography lists the reference material consulted while preparing these pages.

The NuGet client ships inside every .NET SDK, inside Visual Studio and as nuget.exe, each on its own schedule. This page shows how to find the version in use, maps NuGet versions to the SDKs and Visual Studio releases that carry them, and collects the release history the other NuGet pages cite. The baseline is NuGet 7.9.0, in .NET SDK 10.0.400 and 10.0.402.

Finding the version

dotnet nuget --version
7.9.0-rc.611+a8dd0577c5c13f43a2f57fe33b4ff11b90f6371e.a8dd0577c5c13f43a2f57fe33b4ff11b90f6371e

The SDK carries a build labelled as a release candidate of 7.9.0 — the SDK’s internal dependency label; the functionality is that of NuGet 7.9.0. The commit after + is the SDK’s. In Visual Studio, Help > About lists the NuGet Package Manager version; nuget.exe help prints its own.

nuget.exe releases are listed in a JSON feed:

curl -s https://dist.nuget.org/tools.json | jq -r '."nuget.exe"[:4][] | "\(.version) \(.stage) \(.uploaded[:10])"'
7.9.0 ReleasedAndBlessed 2026-08-11
7.6.0 ReleasedAndBlessed 2026-05-12
7.3.1 ReleasedAndBlessed 2026-04-14
7.3.0 ReleasedAndBlessed 2026-02-10

Source: Install NuGet client tools: Support policy, NuGet tools release feed.

Mapping

NuGet .NET SDK Visual Studio

6.8

8.0.100

2022 17.8

6.9

8.0.200

2022 17.9

6.10

8.0.300

2022 17.10

6.11

8.0.400

2022 17.11

6.12

9.0.100

2022 17.12

6.13

9.0.200

 — (the release notes list no Visual Studio version for 6.13.0)

6.14

9.0.300

2022 17.14

7.0

10.0.100

2026 18.0

7.3

10.0.200

2026 18.3

7.4, 7.5

 — (Visual Studio-only)

2026 18.4, 18.5

7.6

10.0.300

2026 18.6

7.7, 7.8

 — (Visual Studio-only)

2026 18.7, 18.8

7.9

10.0.400 (baseline 10.0.402)

2026 18.9

7.10

 — (Visual Studio-only)

2026 18.10

8.0 (preview)

11.0.100-rc.2 (8.0.0-rc.47512)

 — 

Since NuGet 7, versions that ship with an SDK band alternate with Visual Studio-only releases, whose release-notes pages say so and list "N/A" for the SDK. There are no release-notes pages for 7.1 and 7.2 (the URLs return 404), and no page for 8.0 yet. A repository built with both Visual Studio 18.10 (NuGet 7.10) and SDK 10.0.402 (NuGet 7.9) can therefore see slightly different restore behaviour in the IDE and on the command line.

Source: NuGet 7.0 release notes, NuGet 7.4 release notes, NuGet 7.9 release notes, NuGet 7.10 release notes.

Release history

NuGet SDK / VS Change

4.3

SemVer 2.0.0 versions

4.9

VS 15.9

lock files (packages.lock.json); trusted signers

5.0

VS 16.0

GeneratePathProperty

5.7

VS 16.7

PackageReference aliases (notes)

5.9

5.0.200

dotnet list package --vulnerable (notes)

6.0

6.0.100 / VS 2022

package source mapping; vulnerability and deprecation info in the package manager UI (notes)

6.2

6.0.3xx / VS 17.2

CPM VersionOverride; NU1507 (notes)

6.3

VS 17.3

NU1803 HTTP-source warning (notes)

6.4

7.0.100 / VS 17.4

Central Package Management production ready; GlobalPackageReference (notes)

6.5

7.0.200

dotnet list package --format json (notes)

6.8

8.0.100

NuGetAudit; allowInsecureConnections; signature verification on by default on Linux (notes)

6.9

8.0.200

dotnet package search; CPM floating versions; --no-cache renamed --no-http-cache (notes)

6.10

8.0.3xx

dotnet nuget config; NuGetAudit for packages.config (notes)

6.11

8.0.400

dotnet nuget why; NuGetAuditSuppress; --allow-insecure-connections (notes)

6.12

9.0.100

the new dependency resolver; auditSources; HTTP sources are an error (NU1302); SHA-1 fingerprints deprecated (notes)

6.13

9.0.200

PrunePackageReference opt-in; credential providers found on PATH (as .NET tools) (notes)

6.14

9.0.300

.slnx support; --vulnerable honours auditSources (notes)

7.0

10.0.100 / VS 18.0

**NuGetAuditMode=all for net10.0**; package pruning on for `net10.0`; dotnet package update --vulnerable; project.json removed; NuGet MCP server; noun-first dotnet package commands

7.3

10.0.200

dotnet package download (notes)

7.6

10.0.300

duplicate frameworks (NU1018, NU1019); push API key from an environment variable (notes)

7.9

10.0.400

nuget why reports the real transitive versions; NU1703 (MonoAndroid deprecated)

8.0 (preview)

.NET 11 SDK

minimum publish age (minPublishAgeHours, --min-publish-age-hours, NU1020)

The 4.3, 4.9 and 5.0 rows come from the feature pages that cite them (versioning, lock files, GeneratePathProperty); their release notes are not at the nuget-4.3-style URLs. Two dates on the documentation pages conflict with the release notes — dotnet nuget config (8.0.2xx on its pages, 6.10 / 8.0.3xx in the notes) and --allow-insecure-connections (".NET 9" on its page, 6.11 / 8.0.400 in the notes) — and are discussed on dotnet package and nuget Commands and Package Sources and Source Mapping.

Common mistakes

  • Assuming the IDE and the CLI run the same NuGet — Visual Studio-only releases are newer.

  • Reading the -rc label as a preview — it is the SDK’s build label for the release.

  • Downloading nuget.exe without checking the stage — prefer "ReleasedAndBlessed" versions from tools.json.

References