Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

I am totally underqualified to review this PR. :)

But out of curiosity, I wonder if it would make sense to start performing cleanup of this as RIDs drop off. For instance, netcoreapp2.0 and netcoreapp3.0 are out of support, netcoreapp2.1 will be out of support by the time this wave ships, and so on. It doesn't affect this PR in any way, but it makes me wonder if we should do a grand pass of this and all of our ref\*.csproj and src\*.csproj files.

It doesn't affect this PR in any way, but it makes me wonder if we should do a grand pass of this and all of our ref*.csproj and src*.csproj files.

• Upgrade netcoreapp2.x package assets to netcoreapp3.x #46400
• Haven't filed an issue for upgrading anything to net461 yet but it's planned as well.

After removing harvested assets, this would be the next iteration of trimming out package assets that aren't applicable to modern workloads anymore.

I kicked the staging step again, but CI looked green otherwise.

But out of curiosity, I wonder if it would make sense to start performing cleanup

This whole validation process should be wholesale replaced with the shipping functionality that @safern and @anpik are working on. PackageIndex, SupportedFramework, etc will go away 🤞

@ericstj @safern Is there any other signoff or validation we're waiting for?

Nope, this looks good.