Currently this project uses 3 separate feeds to restore packages:
The dotnet-public feed under dev.azure.com/dnceng/public (used as the default feed)
The dotnet-myget-legacy feed under dev.azure.com/dnceng/public (used for the old version of Microsoft.Extensions.CommandLineUtils.Sources we still use)
The msft_consumption feed under dev.azure.com/azure_public/vside.
The last is most concerning: the feed is meant for consumption as an upstream (hence "consumption" in the name) and will eventually purge package versions as they age. This makes it unreliable to depend upon long-term.
The ideal configuration would be to have a public ADO feed with these 3 as upstreams. Originally public feeds did not support upstreams other than nuget.org, which is why it wasn't a solution for this project in the past. Now support for upstreams has been added, we can consolidate better.
Currently this project uses 3 separate feeds to restore packages:
The last is most concerning: the feed is meant for consumption as an upstream (hence "consumption" in the name) and will eventually purge package versions as they age. This makes it unreliable to depend upon long-term.
The ideal configuration would be to have a public ADO feed with these 3 as upstreams. Originally public feeds did not support upstreams other than nuget.org, which is why it wasn't a solution for this project in the past. Now support for upstreams has been added, we can consolidate better.