-
Notifications
You must be signed in to change notification settings - Fork 4.9k
[master] Update dependencies from dotnet/arcade #36103
[master] Update dependencies from dotnet/arcade #36103
Conversation
…312.7 This change updates the following dependencies - Microsoft.DotNet.ApiCompat - 1.0.0-beta.19162.7 - Microsoft.DotNet.XUnitExtensions - 2.4.0-beta.19162.7 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19162.7 - Microsoft.DotNet.Build.Tasks.Configuration - 1.0.0-beta.19162.7 - Microsoft.DotNet.Build.Tasks.Feed - 2.2.0-beta.19162.7 - Microsoft.DotNet.Build.Tasks.Packaging - 1.0.0-beta.19162.7 - Microsoft.DotNet.CodeAnalysis - 1.0.0-beta.19162.7 - Microsoft.DotNet.CoreFxTesting - 1.0.0-beta.19162.7 - Microsoft.DotNet.GenAPI - 1.0.0-beta.19162.7 - Microsoft.DotNet.Helix.Sdk - 2.0.0-beta.19162.7 - Microsoft.DotNet.SourceRewriter - 1.0.0-beta.19162.7 - Microsoft.DotNet.GenFacades - 1.0.0-beta.19162.7
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@mmitche, @safern, I don't know where the problem stems from, but all legs are failing with errors like this:
|
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@JohnTortugo Is this related to the release pipeline work? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
I don't think it is. Looks more something related to packaging. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@ericstj and I just took a look, it seems what it broke it was this change: dotnet/arcade#2091 because it bumped the NuGet version to a greatest version of what MSBuild depends on. So basically this is exposing an MSBuild bug that doesn't let you use newer versions of the assemblies that they directly depend on. I guess the right direction is to close until that change in arcade is reverted or we find a workaround to not hit these issues. @ericstj is opening an issue in MSBuild and we'll follow up with the arcade changes. |
@tmat for corefx's purposes I think using 4.9.2 would be enough, but I don't know for other repos. Would you mind jumping on this? |
@safern Well, we need that change to generate correct license metadata to the packages. Which MSBuild version are we talking about? Can we use newer msbuild? |
4.9.2 has the required properties needed to generate the correct license metadata. We're currently using sdk: 2.2.103 which has MSBuild 15.9.2 -- if we bump the SDK to 3.0 we would be forcing people to install that SDK globally for VS to work for their development, which I guess we don't want to enforce now. |
Ok, if 4.9.2 works then feel free to change the version to 4.9.2. |
This pull request updates the following dependencies
Updates from https://github.com/dotnet/arcade
Updates from https://github.com/dotnet/arcade