NuGet.org / staged publishing / .NET / software delivery / release management
Staged Publishing on NuGet.org: A Release Gate for .NET Delivery Teams
22/11/2026
NuGet.org now offers staged publishing, letting .NET teams validate packages privately before an authorized maintainer promotes them. Here is what changed and how to evaluate it.
A build that finishes is not the same as a release you meant to ship. NuGet.org now offers staged publishing, open to all package publishers, letting teams prepare and validate packages privately before an authorized maintainer decides to publish them S1. For teams in Egypt, Saudi Arabia and the UAE shipping .NET packages, it adds a checkpoint between 'the build passed' and 'this is live' — useful for release managers, platform teams and maintainers.
A release boundary you control
With a normal push, the upload begins public publishing. Staged publishing inserts a pause: the package still runs through NuGet.org validation — malware scanning, signature checks and repository signing — but stays private until a maintainer promotes it on the website S1. Until then it stays out of public pages, search results and restore operations. Staging is opt-in, so existing push workflows keep working S1.
One limitation to plan around: staging is not a private restore feed, even for the owner, so test packages and their dependencies on a local or private feed first S1. And unlike unlisting, a staged package is not available to consumers at all S1.
Coordinating related packages
Related packages — a library and its integrations — can be collected into a staging group under one staging owner, giving a release-level view S1. Permissions follow the staging owner, so co-owning a package does not grant access to content staged for a different owner S1. Promotion requires a signed-in user with two-factor authentication enabled S1. Group promotion is not atomic: packages move through public distribution independently and may become restorable at different times, so plan for that window S1.
Evaluation checklist for regional delivery teams
Confirm whether any package is security-sensitive or part of a coordinated release that needs a private review step S1.
Ensure an authorized maintainer with two-factor authentication can approve releases S1.
Keep testing packages and dependencies on a local or private feed, since staging is not a private restore feed S1.
For related packages, review each one's validation status in a staging group and plan for non-atomic promotion S1.
These are documented capabilities, not a mandate. Whether staged publishing fits depends on how your team coordinates releases; treat it as one option to evaluate.
Want help reviewing your .NET release process or building reliable delivery pipelines? KION builds custom software and backends, integrations and automation, working remotely with teams across the region. Explore our custom software services or get in touch to discuss your workflow.
Sources
AI-assisted analysis based on the following primary sources.
- [S1] Introducing staged publishing on NuGet.org · Microsoft .NET · 2026-11-17