Question

Your team publishes NuGet packages to an Azure Artifacts feed. Developers continuously push prerelease packages during active development, but downstream consumer teams must only be able to restore packages that have passed QA validation. You want to promote validated packages so consumers can reference a stable set without changing their feed source URL to a different feed. Which approach should you implement?

Accepted Answer

Create separate @Prerelease and @Release views on the feed and promote a package to the @Release view after QA passes; have consumers connect to the @Release view endpoint.

Answer

Create a second Azure Artifacts feed named 'Release' and use a pipeline task to copy validated packages between feeds, pointing consumers at the second feed.

Answer

Configure an upstream source on the consumer feed that pulls only packages tagged as validated from the development feed.

Answer

Apply a retention policy that automatically deletes prerelease packages so only validated stable packages remain visible to consumers.