Technology1 min read

Introducing staged publishing on NuGet.org

By · Published by Everything Blog

In short

Package maintainers gain greater control over their release cycles through a new private staging workflow that runs essential system scans prior to public availability. This opt-in capability keeps packages hidden from public searches and restore feeds while publishers review validation reports or swap out failing components. Because the environment does not operate as a private restore feed, teams must still perform preliminary functional testing on local or external private feeds before uploading their release assets. Promotion requires authorized maintainers to authenticate with two-factor credentials before artifacts move to public distribution.

Key points

  • Promoting staged packages or groups requires an authorized maintainer who is signed in wi…: Promoting staged packages or groups requires an authorized maintainer who is signed in with two-factor authentication.
  • Group promotions are not atomic, meaning individual packages enter distribution independe…: Group promotions are not atomic, meaning individual packages enter distribution independently and may become available at different times.
  • All packages inside a staging group must pass all validation checks before the group can…: All packages inside a staging group must pass all validation checks before the group can be approved for public release.

Sources checked by our analysis pipeline: 1

A successful build tells you that your pipeline finished. It does not tell you that you meant to release. Today, we are introducing staged publishing on NuGet.org, available to all package publishers, so you can prepare and validate packages privately before making an explicit decision to publish them.

Upload a security fix ahead of its coordinated disclosure. Gather the packages for a feature release without exposing an unfinished set. Let automation prepare a large update, then review it on NuGet.org before it reaches the people who depend on it.

Your pipeline prepares the release. You decide when it goes live.

A release boundary you control

With a normal package push, upload starts the public publishing process. Staged publishing adds a place to stop: the package goes through NuGet.org validation, but stays private until an authorized maintainer promotes it through the website.

That gives you time to review what you are about to ship, fix validation problems, and choose the release moment.

Staging is opt-in. Existing dotnet nuget push

workflows continue to work. You can adopt staging for a security-sensitive package…

Technology