Enhanced package upload workflow

Issue

Enhanced package upload workflow

Problem

Going forward, NuGet packages shall undergo validation, in addition to indexing, before they are made available on the gallery and for download from v3/v2 feed. At present, there is no way for the publisher to know if the validation fails, and what to do next.

Who is the customer?

NuGet package publishers would have an intuitive, self-serve way of knowing the current status of the package and would not have to guess and/or reach out to NuGet support.

Evidence

The NuGet team receives tens of requests a week specifically asking for clarification around when a package will be available for consumption while it is being indexed. This problem might get exasperated when we introduce package validation as part of this flow.

Solution

Modified workflow

Here is the workflow when a package is pushed:

(you may have to zoom-in up to 160%)

Package page showing the status

This page will be visible only to the package owner/s.

Post validation and indexing

Once the package has been validated and indexed, the status info bar goes away, the package page becomes public, the package is made available for download from the gallery and for consumption through the v2/v3 feeds, and an email notification is sent to the owners informing them that the package has been published.

Issues with validation