NuGet.org has introduced staged publishing, a new feature that allows package publishers to upload packages for validation without immediately making them public. Unlike a normal package push, staged publishing adds an intermediate step where packages undergo NuGet.org's validation process but remain private. An authorized maintainer must then explicitly promote the package through the website for it to become publicly available.
This new capability provides publishers with time to review content before release, address any validation problems, and precisely control the release moment. It is particularly useful for scenarios such as uploading security fixes ahead of coordinated disclosure, gathering packages for a feature release without exposing an unfinished set, or allowing automation to prepare updates for manual review.
Staging is an opt-in feature, meaning existing `dotnet nuget push` workflows will continue to function as before. Publishers can adopt staging for specific security-sensitive packages or coordinated releases without altering all their publishing workflows.
Staged publishing differs from unlisting a package. An unlisted package can still be restored by its exact version, whereas a staged package is completely unavailable to consumers. Staged packages do not appear in public package pages, search results, or restore operations.
Publishers can stage packages by selecting the staging option on the NuGet.org upload page or via the CLI. NuGet.org then runs the package through its validation pipeline, including malware scanning, signature checks, and repository signing. Once validation is successful, the package is ready for promotion. Publishers can inspect staged packages and their validation status within the website's package management interface. Staging does not provide a private restore feed; testing of packages and dependencies should occur using local or private feeds prior to staging release artifacts.
The feature also allows for the organization of related packages into a 'staging group,' which collects multiple packages for a release under a single staging entity.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
NuGet.org has launched staged publishing, allowing package publishers to upload and validate packages privately before making them publicly available. This feature provides a controlled release boundary, enabling maintainers to review packages, fix validation issues, and decide the exact publication time, which is useful for security fixes or coordinated feature releases.