-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[main] Update dependencies from dotnet/windowsdesktop #47992
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/windowsdesktop #47992
Conversation
…ld 20250328.1 Microsoft.WindowsDesktop.App.Ref , Microsoft.WindowsDesktop.App.Runtime.win-x64 , VS.Redist.Common.WindowsDesktop.SharedFramework.x64.10.0 , VS.Redist.Common.WindowsDesktop.TargetingPack.x64.10.0 From Version 10.0.0-preview.4.25177.2 -> To Version 10.0.0-preview.4.25178.1 Dependency coherency updates Microsoft.NET.Sdk.WindowsDesktop,Microsoft.Dotnet.WinForms.ProjectTemplates,Microsoft.DotNet.Wpf.ProjectTemplates From Version 10.0.0-preview.4.25177.1 -> To Version 10.0.0-preview.4.25178.3 (parent: Microsoft.WindowsDesktop.App.Ref
Notification for subscribed users from https://github.com/dotnet/windowsdesktop:@dotnet/wpf-developers Action requested: Please take a look at this failing automated dependency-flow pull request's checks; failures may be related to changes which originated in your repo.
|
…ld 20250328.2 Microsoft.WindowsDesktop.App.Ref , Microsoft.WindowsDesktop.App.Runtime.win-x64 , VS.Redist.Common.WindowsDesktop.SharedFramework.x64.10.0 , VS.Redist.Common.WindowsDesktop.TargetingPack.x64.10.0 From Version 10.0.0-preview.4.25177.2 -> To Version 10.0.0-preview.4.25178.2
…ld 20250329.1 Microsoft.WindowsDesktop.App.Ref , Microsoft.WindowsDesktop.App.Runtime.win-x64 , VS.Redist.Common.WindowsDesktop.SharedFramework.x64.10.0 , VS.Redist.Common.WindowsDesktop.TargetingPack.x64.10.0 From Version 10.0.0-preview.4.25177.2 -> To Version 10.0.0-preview.4.25179.1
@dotnet/source-build @dotnet/product-construction PTAL |
…-tests-in-VMR.patch
@carlossanlop some .NET Framework msbuild tests are failing because of the System.Runtime.CompilerServices.Unsafe/6.1.0 package update. In this case I bet that something is loading the newer CU assembly into a desktop msbuild task host. Can you please take a look? Looks like this affects all PRs in dotnet/sdk. Presumably a PR with the failures got force merged. |
Why are those PRs getting auto-merged with a failing job? That should be fixed asap. In this case it's fine because the regression already happened in #47898. cc @marcpopMSFT - probably BuildAnalysis related |
@ViktorHofer the |
Right. But IIRC the "Build Analysis" leg should be marked as required and check whether the |
dotnet/dnceng#3327 is probably the tracking issue for this. cc @missymessa |
It was suggested we use BA is the primary check but that doesn't work because of 3327 and we were told not to allow people to override the check on sourcebuild/unified build so we landed with this compromise. I guess in the case where the public PR build is still running but the other builds have completed, we hit 3327 and things get merged. Should I add the CI leg back and hold off using BA until that issue is resolved? |
Based on PRs with failing tests getting merged, I would say yes. We need resolution on dotnet/dnceng#3327 and then decide if we can again gate auto-merge on the Build Analysis job. We had to disable auto-merge in runtime for that exact reason. |
This pull request updates the following dependencies
Coherency Updates
The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format
From https://github.com/dotnet/windowsdesktop