Programming and Software Development

Launch of "Staged Publishing" on NuGet.org: A New Step for Securing and Managing Software Packages

The new "Staged Publishing" feature allows software developers to upload packages, verify their integrity, and prepare them privately on the NuGet.org platform before making the final decision to publish them to the public.

2026-11-17
3 min read
14 views
certi.news Editorial Team
Launch of "Staged Publishing" on NuGet.org: A New Step for Securing and Managing Software Packages

Microsoft has announced the launch of the Staged Publishing feature on the NuGet.org platform, a feature that gives developers and companies the ability to upload software packages and validate them in a private environment before approving their public release. This step aims to bridge the gap between automation processes and the need for careful human review before updates reach end users.

Mechanism and Integrity Verification

Once a package is uploaded using the "Staged Publishing" mode, it undergoes a rigorous inspection process that includes malware scanning, digital signature verification, and repository signing. The package remains in a "private" state; meaning it does not appear in search results and cannot be restored by users until it is promoted via the website.

The promotion process requires administrators to log in with Two-Factor Authentication (2FA) enabled to ensure that no package is published without explicit and confirmed authorization. Developers can also organize related packages (such as a software library with its analysis tools) into Staging Groups, allowing them to review the verification status of each package within the group and ensure it is fully ready before approving the release of the entire group with a single click.

Command Line Interface (CLI) Support

Support for this feature has already begun in the .NET 11 RC2 development kit, where the dotnet package stage push command can be used to upload packages to the staged publishing mode directly from build pipelines. However, the promotion process remains restricted to the website interface to ensure a human element in the decision-making process.

Why does this development matter to developers?

This update represents a shift in how the software lifecycle is managed in sensitive work environments. Instead of relying entirely on automation that might publish an incomplete package or one containing a technical error as soon as the build process succeeds, this feature provides a human "checkpoint" that ensures the quality and reliability of what is released.

Key practical benefits include:

  • Cybersecurity: The ability to upload security fixes and prepare them before the official announcement of a vulnerability (Coordinated Disclosure), which prevents the leak of the fix before users are protected.
  • Control over large releases: Grouping all components related to a new feature and ensuring their compatibility before releasing them all at once.
  • Reducing hacking risks: Using API keys dedicated only to staging (Staging-only) reduces the risks of pipeline compromises; a hacker would be able to upload a package for review, but they would not be able to publish it directly to the public.

Technical Note: It should be noted that the bulk publishing of groups is not "atomic," meaning that packages may become available to users at slightly different times during the distribution process across the NuGet network.

News source
c
Author

certi.news Editorial Team

In the same category

You may also like

View all news