-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[main] Update dependencies from dotnet/arcade #12873
[main] Update dependencies from dotnet/arcade #12873
Conversation
…203.6 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.CMake.Sdk , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.XUnitExtensions From Version 10.0.0-beta.25074.4 -> To Version 10.0.0-beta.25103.6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go, you big red fire engine!
…204.2 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.CMake.Sdk , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.XUnitExtensions From Version 10.0.0-beta.25074.4 -> To Version 10.0.0-beta.25104.2
b8b4697
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #12873 +/- ##
===================================================
- Coverage 76.13460% 76.09624% -0.03837%
===================================================
Files 3251 3255 +4
Lines 642520 642882 +362
Branches 47286 47315 +29
===================================================
+ Hits 489180 489209 +29
- Misses 149798 150114 +316
- Partials 3542 3559 +17
Flags with carried forward coverage won't be shown. Click here to find out more. |
…s started to fail on th epublising stage. https://dev.azure.com/dnceng/internal/_build/results?buildId=2637287&view=results This stage reads the "BAR manifests" - a list of our nuget packages that looks like this <Package Id="Microsoft.Dotnet.WinForms.ProjectTemplates" Version="10.0.0-preview.2.25106.1" NonShipping="true" Visibility="External"/> <Package Id="Microsoft.Private.Winforms" Version="10.0.0-preview.2.25106.1" NonShipping="true" Visibility="External"/> <Package Id="System.Drawing.Common" Version="10.0.0-preview.2.25106.1" DotNetReleaseShipping="true" Visibility="External"/> <Package Id="System.Private.Windows.Core.TestUtilities" Version="10.0.0-preview.2.25106.1" NonShipping="true" Visibility="External"/> "BAR manifest" is generated on the "Pack Sign and Publish" step. Before the PR from arcade, this step was generating manifest named AssetManifest\Windows_NT-AnyCPU.xml for each architecture, overriding the previously written one inplace. Then the publish step was processeng that manifest. After the arcade PR we are generating 3 manifests, one for each architecture. Windows_Arm64.xml Windows_x64.xml Windows_x86.xml probably because of this change dotnet/arcade@232c628 We need only a single manifest and a single set of the nugets, thus we should run the publishing step only for x64. I don't know why build-PR script has the "Pack, Sign. publish" step because it does not actually run "Skipping step due to condition evaluation." I think this step can only run in AzDO (looking at publish.proj in arcade) I'm open to removing this step.
…ted to fail on th epublising stage. https://dev.azure.com/dnceng/internal/_build/results?buildId=2637287&view=results This stage reads the "BAR manifests" - a list of our nuget packages that looks like this <Package Id="Microsoft.Dotnet.WinForms.ProjectTemplates" Version="10.0.0-preview.2.25106.1" NonShipping="true" Visibility="External"/> <Package Id="Microsoft.Private.Winforms" Version="10.0.0-preview.2.25106.1" NonShipping="true" Visibility="External"/> <Package Id="System.Drawing.Common" Version="10.0.0-preview.2.25106.1" DotNetReleaseShipping="true" Visibility="External"/> <Package Id="System.Private.Windows.Core.TestUtilities" Version="10.0.0-preview.2.25106.1" NonShipping="true" Visibility="External"/> "BAR manifest" is generated on the "Pack Sign and Publish" step. Before the PR from arcade, this step was generating manifest named AssetManifest\Windows_NT-AnyCPU.xml for each architecture, overriding the previously written one inplace. Then the publish step was processeng that manifest. After the arcade PR we are generating 3 manifests, one for each architecture. Windows_Arm64.xml Windows_x64.xml Windows_x86.xml probably because of this change dotnet/arcade@232c628 We need only a single manifest and a single set of the nugets, thus we should run the publishing step only for x64. I don't know why build-PR script has the "Pack, Sign. publish" step because it does not actually run "Skipping step due to condition evaluation." I think this step can only run in AzDO (looking at publish.proj in arcade) I'm open to removing this step.
This pull request updates the following dependencies
From https://github.com/dotnet/arcade
Microsoft Reviewers: Open in CodeFlow