[release/7.0] Flow internal transport packages during servicing #75979
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This makes sure that partner repositories have their internal transport packages available. This needs to be set explicitly as during servicing, libraries only publish on demand. This also fixes broken 7.0 servicing builds which require at least one package to be published. Manual, partial backport of c5a20f9.
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBackport of #75969 to release/7.0 /cc @ViktorHofer Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
|
@danmoseley @ericstj this is a tell-mode only change necessary for servicing .NET 7. This came-up in the ".NET 7 Stable Test Build" exercise. For more details please see the underlying PR that targets main. |
|
Not needed for RC2? |
|
No. This won't be necessary until we service .NET 7 which presumably is 7.0.1. |
|
There's a CI failure I haven't seen before. Could it be related to this PR? runtime-staging (Build Browser wasm windows Release LibraryTests) cc @eiriktsarpalis in case you've seen this. |
|
@carlossanlop I haven't, but that particular path points to an F# test project. IIRC we've had sdk related issues with that project in the past. |
ghost
locked as resolved and limited conversation to collaborators
Backport of #75969 to release/7.0
/cc @ViktorHofer
Customer Impact
Testing
Risk
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.