Official build break in publish stage: NuGet library mismatch vs. SDK

[dagood]

First repro: https://dev.azure.com/dnceng/internal/_build/results?buildId=499590&view=results

D:\a\1\s.packages\microsoft.dotnet.arcade.sdk\5.0.0-beta.20071.3\tools\SdkTasks\PublishArtifactsInManifest.proj(65,5): error : Method not found: 'NuGet.Versioning.NuGetVersion NuGet.Packaging.Core.PackageIdentity.get_Version()'.

This is a common class of issue where the Arcade SDK is built against a certain NuGet version, but the SDK contains another that is incompatible when used at runtime. We recently updated the SDK, triggering it.

We need to update the Arcade SDK to take this fix: dotnet/arcade#1965

runtime/global.json

Line 15 in 110af6e

"Microsoft.DotNet.Arcade.Sdk": "5.0.0-beta.20071.3",

We need at least 5.0.0-beta.20074.6.

[jkoritzinsky]

Our maestro PR is currently blocked on something. It looks like it might be linker issues. #2074

[dagood]

Alternative: downgrade the SDK. (Optionally, disable restoring internal tools to also remove flakiness.)

[dagood]

FYI @dotnet/runtime-infrastructure

[safern]

(Optionally, disable restoring internal tools to also remove flakiness.)

I just merged a PR which should hopefully help with that.

[jkoritzinsky]

I’d rather not downgrade the SDK since to unblock #2115 and dotnet/sdk#3884 I need to update to an SDK with #2264 once that’s published (which would be after we fix this, but would lead us back to the same problem very quickly).

I think we should either update our dotnet/arcade subscription or back out the linker upgrade from the Maestro PR until the blocking issue is fixed.

[ViktorHofer]

I just removed the linker update (again) and disabled the subscription (again) to get the Arcade update in. @marek-safar is following-up on the break illink.

#2074

[dagood]

Thanks all, new build is green: https://dev.azure.com/dnceng/internal/_build/results?buildId=502394&view=results. 🎉