Skip to content
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

Merged
merged 3 commits into from
Feb 6, 2025

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Feb 4, 2025

This pull request updates the following dependencies

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

  • Subscription: b9a1a4bb-2302-4987-3b3d-08d8b8050dda
  • Build: 20250204.2
  • Date Produced: February 4, 2025 5:21:11 PM UTC
  • Commit: 5d30877b1eb318583acd5f2cd3f3a80e77b3add2
  • Branch: refs/heads/main
Microsoft Reviewers: Open in CodeFlow

…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
@dotnet-maestro dotnet-maestro bot requested a review from a team as a code owner February 4, 2025 11:49
dotnet-policy-service[bot]
dotnet-policy-service bot previously approved these changes Feb 4, 2025
Copy link
Contributor

@dotnet-policy-service dotnet-policy-service bot left a 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
Copy link

codecov bot commented Feb 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.09624%. Comparing base (82f8e2c) to head (b348638).
Report is 14 commits behind head on main.

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     
Flag Coverage Δ
Debug 76.09624% <100.00000%> (-0.03837%) ⬇️
integration 18.09037% <0.00000%> (-0.00616%) ⬇️
production 49.99072% <100.00000%> (-0.09227%) ⬇️
test 96.97113% <ø> (-0.00706%) ⬇️
unit 47.41802% <100.00000%> (-0.09899%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@Tanya-Solyanik Tanya-Solyanik merged commit 7f286b4 into main Feb 6, 2025
9 checks passed
@Tanya-Solyanik Tanya-Solyanik deleted the darc-main-432ec7cd-4bce-4719-b72c-f652d72a555d branch February 6, 2025 02:58
Tanya-Solyanik added a commit to Tanya-Solyanik/winforms that referenced this pull request Feb 8, 2025
…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.
Tanya-Solyanik added a commit that referenced this pull request Feb 10, 2025
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant