[release/8.0.4xx] Bump to dotnet/android-tools@f53106a1#9579
[release/8.0.4xx] Bump to dotnet/android-tools@f53106a1#9579pjcollins merged 5 commits intorelease/8.0.4xxfrom
Conversation
Changes: dotnet/android-tools@d50747c...f53106a * dotnet/android-tools@f53106a: Bump to dotnet/msbuild@10fbfbf2 (#241) * dotnet/android-tools@a2e146d: Bump to dotnet/msbuild@33de0b22 (#232) * dotnet/android-tools@1818d59: Bump LibZipSharp and Xamarin.Build.AsyncTask (#236) * dotnet/android-tools@75f79e7: Bump LibZipSharp to 3.1.1 (#228) * dotnet/android-tools@b1f795e: [MSBuildReferences.projitems] Require opt-in to use `Microsoft.Build` (#220)
|
The failures in |
|
Do we need to do the old |
Yes sorry good catch! it looks like all of monodroids dependencies are up to date but we were missing a couple of bumps in monodroid. I've set that up here https://github.com/xamarin/monodroid/pull/1559 and we can include once merged. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jonathanpeppers
left a comment
There was a problem hiding this comment.
I reran some of the failures to see if it can be slightly greener.
We can ignore the CustomDesignerTargetSetupDependenciesForDesigner test for sure.
|
Thanks, we're down to the two failures in |
With dotnet/android-tools#220, we now need to set
$(_IncludeMicrosoftBuildPackage)for projects that need aMicrosoft.Buildreference.Changes: dotnet/android-tools@d50747c...f53106a
Microsoft.BuildChanges: https://github.com/xamarin/monodroid/compare/b753d75f846b76cabb3b65b52ac12c4a83c07a13...99627fea9cf2ce9ca59fa571ea5640f8eb4a9c59