Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Categorize shipping/nonshipping NuGet packages #7776

Merged
merged 1 commit into from
Aug 20, 2019

Conversation

dagood
Copy link
Member

@dagood dagood commented Aug 20, 2019

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:

  • Add the NonShipping dir as a restore source in a few places so the legacy packages can be found by parts of the infra that still consume them.
  • Fix the 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

@dagood dagood self-assigned this Aug 20, 2019
@dagood dagood merged commit 645aa3a into dotnet:master Aug 20, 2019
@dagood dagood deleted the categorize-artifacts branch August 20, 2019 22:30
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants