The feature is a release checkpoint between "upload" and "public." It is not a private feed, and group promotion is not atomic. Both limits matter when you plan a real release.
What changes in the publishing flow
With a normal push, the upload starts public publishing. With staging, the package goes through NuGet.org validation but stays private until an authorized maintainer promotes it on the website.
- Opt-in. Existing
dotnet nuget pushworkflows keep working. You can adopt staging for one sensitive package or one coordinated release. - Not unlisting. An unlisted package can still be restored by its exact version. A staged package isn't available to consumers at all.
- Hidden everywhere public. Staged packages stay out of public package pages, search results and restore operations.
- Real validation. Staged packages go through malware scanning, signature checks and repository signing.
This addresses an old request. A NuGet/Home GitHub issue asked for a way to upload packages for signature validation and virus scanning, then delete them before publishing if necessary. The requester wanted that for coordinated multi-product releases. Staging covers much of that need, though it works through promotion rather than deletion. The announcement doesn't describe a discard step, so don't assume one.
Staging is not a test feed
Staging does not provide a private restore feed, even for the owner. You can't pull a staged package into a test project from NuGet.org. Microsoft's advice is to test the package and its dependencies against a local or private feed first, then stage the artifacts.
Microsoft's own library guidance already points to local feeds: a local feed is useful for testing a NuGet package before publishing it to NuGet.org. Staging doesn't replace that step. It adds a review gate after it.
How to stage a package
From the website
- Open the NuGet.org upload page.
- Under Publishing Mode, choose the staging option.
- Wait for validation, then check the package and its status in package management.
- If validation fails, fix the problem and stage a replacement before release day.
From the CLI (.NET 11 RC2 SDK)
The RC2 SDK supports basic staging uploads:
dotnet package stage push ./artifacts/Contoso.Library.1.2.0.nupkg \
--source [url]https://api.nuget.org/v3/index.json[/url] \
--api-key "$NUGET_API_KEY"
NUGET_API_KEY should be a staging-capable credential supplied securely by your workflow, never committed to source control. A staging-only key gives the strongest separation.
An accepted upload doesn't mean validation has finished or that the package is public. Go back to NuGet.org to check.
Staging groups for multi-package releases
A staging group collects related packages under one staging owner, which can be a user or an organization. Microsoft's example is a library plus its integrations and analyzers.
To send a push to a group, add --group with an ID:
dotnet package stage push ./artifacts/Contoso.Library.1.2.0.nupkg \
--source [url]https://api.nuget.org/v3/index.json[/url] \
--api-key "$NUGET_API_KEY" \
--group november-release
If the group doesn't exist yet, NuGet.org creates it.
Permissions follow the staging owner. Co-owning a package doesn't automatically give you access to content staged on behalf of a different owner. Teams that mix personal and organization accounts should check this before release day, not during it.
Promotion: where the human comes in
Promotion happens only on the website. Use Promote for a single package or Promote group for a group. The user must be authorized and signed in with two-factor authentication enabled on their account.
Microsoft is explicit about a limit here. Having 2FA enabled and approving in an authenticated session is not a fresh 2FA challenge for each promotion. The post says it is not claiming one. Treat this as a human-presence checkpoint, not step-up authentication.
Before you promote a group:
- Confirm the package IDs and versions match your release plan.
- Confirm dependencies that must ship alongside them are included.
- Resolve any package that is still validating or has failed. These block promotion from starting.
After you promote:
- Watch progress and outcome on the website.
- If one item fails, follow up on that item. Don't assume the whole release landed.
Group promotion is not atomic. Packages move through the public distribution pipeline independently, so they can become restorable at different times. Don't promise simultaneous availability. Sequence announcements, and any consumers that depend on a full set, with that window in mind.
The security angle
The strongest setup gives automation staging-only permissions. A staging-only API key can upload staged packages but can't use the normal push path to publish. Trusted Publishing policies can also be restricted to staging only.
So a stolen pipeline credential can submit content for review but can't release it to consumers directly. Microsoft cautions that this doesn't make the content trustworthy. Review artifacts, investigate unexpected uploads, and keep protecting build systems and maintainer accounts. An attacker who can't publish can still try to slip something into a rushed approval.
Microsoft also recommends pairing staging with Trusted Publishing. Microsoft Learn describes that as replacing long-lived API keys with short-lived credentials from your CI/CD system, such as GitHub Actions. Per that documentation, NuGet's temporary API keys are valid for one hour, and each token can be exchanged only once. Trusted Publishing limits what a leaked credential is worth. Staging adds the approval step it doesn't provide on its own.
Limits and open questions
- CLI coverage is partial. Listing and group management are planned for a future SDK update. The proposed commands include
dotnet package stage listanddotnet package stage group create. Microsoft labels these roadmap examples, not final syntax or a release date. - No CLI approval. Promotion stays a website action, so don't plan on scripting it.
- Expiration exists, but no duration is given. Staged content expires if it isn't promoted. The announcement doesn't say how long that takes, so check expiry notices for longer release cycles.
- RC SDK dependency. CLI staging needs the .NET 11 RC2 SDK. Pin that version in any pipeline you test with.
A sensible rollout
- Pick one low-risk package, or a small group.
- Test the artifacts and dependencies on a local or private feed.
- Stage them and review validation on NuGet.org.
- Give the pipeline staging-only credentials, and consider a staging-only Trusted Publishing policy.
- Have an authorized maintainer promote.
- Time how long promoted packages take to become restorable, and note the expiry behavior.
Rehearse before you need it for a coordinated security disclosure. That is when you least want to learn that a co-owner can't see a group staged under someone else's account.
The release boundary is useful because a person has to cross it. It won't catch a bad package for you, but it gives someone a defined moment to look at what is about to reach other people's builds.
References
- Introducing staged publishing on NuGet.org .NET Blog · 2026-11-17T21:00:00+00:00
- Provide option to upload packages for verification and be staged but unpublished. · Issue #8556 · NuGet/Home · GitHub github.com
- publish nuget package learn.microsoft.com