Microsoft's NuGet team opened staged publishing to every package publisher on NuGet.org on November 17, 2026. A staged package goes through the normal validation steps but stays hidden until an authorized maintainer promotes it on the website.
The change splits two steps that used to happen together: uploading a package and releasing it. For .NET library authors this means a build pipeline can prepare a release without making it public, which matters for security fixes, coordinated multi-package releases and supply chain protection.
What Staged Publishing Changes
Until now, a push to NuGet.org started the public release process right away. With staging, the upload stops at a holding point after validation, and the package is kept out of package pages, search results and restore operations.
The feature is opt-in. Existing dotnet nuget push workflows keep working, so teams can try staging on one sensitive package without changing every pipeline. Microsoft also points out how this differs from unlisting: anyone who knows the exact number of an unlisted version can still pull it, while a staged one is off limits to everybody.
Key points of the new flow:
- Staged packages still pass through malware scanning, signature checks and repository signing.
- Related packages can be collected into a staging group owned by a user or an organization.
- Promotion happens only on the NuGet.org website, by a signed-in user who has two-factor authentication turned on.
- Staged content expires if nobody promotes it, so it is a short preparation window rather than storage.
How Staging Groups and Promotion Work
A staging group lets a team gather, for example, a core library together with its integration packages and analyzers for one feature release. The website shows each package's validation status in one view, and a maintainer can promote a single package or the whole group in one action.
Group promotion is not atomic, though. Each package moves through the public distribution pipeline on its own, so packages in the same group may become restorable at slightly different times. Anything that fails or is still validating must be fixed before group promotion can start.
Permissions follow the staging owner. Co-owning a package does not let you see items that another owner put into staging. There is also no private restore feed for staged packages, even for the owner, so you should test builds against a local or private feed before staging them.
Staging From the .NET CLI
Starting with the .NET 11 RC2 SDK, the CLI can upload a package for staging instead of publishing it. The new dotnet package stage push command takes the .nupkg path, the NuGet.org source URL and an API key, plus an optional --group name.
When a group name is given, NuGet.org creates the group if it does not exist yet. A successful upload only means the package was accepted; you still return to the website to check validation and promote it. Commands for listing staged packages and managing groups are planned for a later SDK, and Microsoft says approval will stay a website-only action.
Why It Matters for Supply Chain Security
The strongest benefit comes when automation gets staging-only rights. NuGet.org now offers API keys limited to staged uploads that are refused on the regular publish route, and Trusted Publishing policies can be limited to staging as well.
If such a pipeline credential leaks, an attacker can only submit content for review rather than ship it straight to users. Microsoft is careful to say this does not make staged content trustworthy by itself, and it does not mean a fresh two-factor prompt on every promotion. Maintainers still need to review what was uploaded and watch for unexpected submissions.
What It Means for Developers
If you maintain public NuGet packages, the quickest win is to issue a staging-only API key for your CI system and keep the full push key off build agents. Pair it with Trusted Publishing so the pipeline uses short-lived credentials rather than stored secrets.
For security fixes, staging lets you upload and validate the patched package before the disclosure date, then promote it at the agreed time. Rehearse the flow once before you need it, and measure how long promoted packages take to become restorable so your release notes do not go out too early.
Package consumers do not need to do anything. They simply will not see a version until the maintainer approves it. For other recent .NET changes, see our coverage of the .NET 11 and C# 15 release and the November .NET security updates.
Conclusion
Staged publishing gives NuGet.org a release checkpoint between a finished build and a public package. It is optional, works with existing pipelines, and is most useful when CI keys are limited to staging so that a person makes the final call on every release.
Sources
See my articles more often when you search Google.
