This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Categorize shipping/nonshipping NuGet packages #7776
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For https://github.com/dotnet/core-setup/issues/6893.
The past few releases have seen some manual intervention to get legacy packages off the NuGet gallery. Marking legacy packages NonShipping fixes this. It changes the category in BAR so release automation won't pick them up.
A few tweaks necessary after categorizing because of the directory change:
prepare-artifacts
job to find the right symbol packages. Symbol packages are always shipping, so we can no longer find them in the same directory as the legacy nupkgs.Here's what's marked NonShipping now (https://gist.github.com/dagood/fc86b7332b60d381121b145ea838b32f):
Microsoft.NETCore.App
Microsoft.NETCore.App.Internal
Microsoft.WindowsDesktop.App
runtime.*.Microsoft.NETCore.App
runtime.*.Microsoft.WindowsDesktop.App
VS.Redist.Common.*
/cc @mmitche @wtgodbe @nguerrera