Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Apr 9, 2025

This pull request updates the following dependencies

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

…408.7

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions
 From Version 8.0.0-beta.25164.5 -> To Version 8.0.0-beta.25208.7
@ghost ghost added the area-codeflow for labeling automated codeflow label Apr 9, 2025
@carlossanlop carlossanlop added the Servicing-approved Approved for servicing release label Apr 11, 2025
@carlossanlop
Copy link
Contributor

Lots of network failures. Restarting the CI by updating the branch.

@carlossanlop
Copy link
Contributor

@lewing @steveisok @akoeplinger there is a consistent build failure only in this deps flow affecting wasm tests. Can one of you please take a look? This is the only deps flow I was unable to merge and include in the flow from staging to internal.
https://github.com/dotnet/runtime/pull/114441/checks?check_run_id=40548750772

I'll temporarily re-enable the arcade subscription to the base branch and see if the failure happens there too. If a fix is needed, we can fix it there to avoid having to flow again from staging to internal.

…414.7

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions
 From Version 8.0.0-beta.25164.5 -> To Version 8.0.0-beta.25214.7
@carlossanlop
Copy link
Contributor

I'll temporarily re-enable the arcade subscription to the base branch and see if the failure happens there too. If a fix is needed, we can fix it there to avoid having to flow again from staging to internal.

Here's the base branch flow: #114667

@akoeplinger
Copy link
Member

The version in global.json got bumped, fixed.

See this comment in Versions.props:

runtime/eng/Versions.props

Lines 271 to 273 in 41a4a37

<!-- installer version, for testing workloads must be greater than or equal to global.json sdk version -->
<MicrosoftDotnetSdkInternalVersion>8.0.115</MicrosoftDotnetSdkInternalVersion>
<SdkVersionForWorkloadTesting>$(MicrosoftDotnetSdkInternalVersion)</SdkVersionForWorkloadTesting>

@carlossanlop
Copy link
Contributor

Thanks, I'll make sure to cherry-pick the same fix for the base branch arcade flow.

@carlossanlop
Copy link
Contributor

/ba-g failure is #88027

@carlossanlop carlossanlop merged commit f8a6297 into release/8.0-staging Apr 15, 2025
188 of 193 checks passed
@dotnet-maestro dotnet-maestro bot deleted the darc-release/8.0-staging-0871dfb3-eb3e-494c-8fd4-1527f9ef449b branch April 15, 2025 17:04
@github-actions github-actions bot locked and limited conversation to collaborators May 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-codeflow for labeling automated codeflow Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants