[master] Update dependencies from dotnet/arcade

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/dotnet/arcade

• Subscription: 3a1d3bb6-c64d-406d-e8f4-08d648cf64cb
• Build: 20200109.3
• Date Produced: 1/9/2020 9:03 PM
• Commit: 96a4497b2c38c6b7e19c39e4cb8fe5adac299fb4
• Branch: refs/heads/master
• Updates:
  • Microsoft.DotNet.ApiCompat -> 5.0.0-beta.20059.3
  • Microsoft.DotNet.Arcade.Sdk -> 5.0.0-beta.20059.3
  • Microsoft.DotNet.CodeAnalysis -> 5.0.0-beta.20059.3
  • Microsoft.DotNet.GenAPI -> 5.0.0-beta.20059.3
  • Microsoft.DotNet.Helix.Sdk -> 5.0.0-beta.20059.3

Fixes #2414

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)

[vatsan-madhavan]

@rladuca Looks like there are significant ApiCompat failures blocking this PR....

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful Unsuccessful checks: dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)

[rladuca]

It looks like this is blocked due to changes from dotnet/arcade#2208.

The generated files have incorrect code in them of the form:

/// <summary>Value of {0} is outside of the allowed range.</summary>
internal const string @ArgumentOutOfRange = "ArgumentOutOfRange");
/// <summary>The value of {0} cannot be changed while the inertia processor is running.</summary>
internal const string @CannotChangeParameterDuringInertia = "CannotChangeParameterDuringInertia");

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful Unsuccessful checks: dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)

[rladuca]

@rladuca Looks like there are significant ApiCompat failures blocking this PR....

The changes in this commit dotnet/arcade@2fdcfc2#diff-9b7e2af6cbe16f7c69be4a9cc5ae4418 are causing the extra ApiCompat errors.

I'm going through the diffs now to make sure that we can baseline them all away. They should all be fine considering we didn't get any bugs filed yet, but double checking to ensure that we no longer need the non-security attributes it complains about (security can obviously be baselined).

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful Unsuccessful checks: dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)

[rladuca]

Fixes #2414

[dotnet-maestro]

Auto-Merge Status

This pull request has been merged because the following merge policies have succeeded.

• ✔️ All Checks Successful Succeeded - Successful checks: auto-merge.config.enforce, dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)