Skip to content

Conversation

@dotnet-maestro
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Dec 5, 2025

This pull request updates the following dependencies

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

…203.3

On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 10.0.0-beta.25555.6 -> To Version 10.0.0-beta.25603.3
@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2025

✅ No release notes required

…205.3

On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 10.0.0-beta.25555.6 -> To Version 10.0.0-beta.25605.3
…208.3

On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 10.0.0-beta.25555.6 -> To Version 10.0.0-beta.25608.3
@T-Gro
Copy link
Member

T-Gro commented Dec 9, 2025

@abonie :

This now tells:
Build FAILED.

D:\a_work\1\s.dotnet\sdk\10.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(145,5): error NETSDK1233: Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported. [D:\a_work\1\s\src\Microsoft.FSharp.Compiler\Microsoft.FSharp.Compiler.fsproj]
D:\a_work\1\s.dotnet\sdk\10.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(145,5): error NETSDK1233: Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported. [D:\a_work\1\s\src\fsi\fsiProject\fsi.fsproj::TargetFramework=net10.0]
D:\a_work\1\s.dotnet\sdk\10.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(145,5): error NETSDK1233: Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported. [D:\a_work\1\s\src\Compiler\FSharp.Compiler.Service.fsproj::TargetFramework=net10.0]
D:\a_work\1\s.dotnet\sdk\10.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(145,5): error NETSDK1233: Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported. [D:\a_work\1\s\src\fsc\fscProject\fsc.fsproj::TargetFramework=net10.0]
0 Warning(s)
4 Error(s)

Do we have any leftover windows2022 images? Or is it only because of the dev18.0 brach?

@abonie
Copy link
Member

abonie commented Dec 9, 2025

@T-Gro I can tell that with these changes for this PR the tests are run on vs2022
image
while for other PRs they currently run on vs2026, but it is not immediately obvious to me why this PR makes it so that it reverts to vs2022 images

edit: Sorry, I missed that it's a PR to release/dev18.0, this one runs on vs2022 image it seems

…209.2

On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 10.0.0-beta.25555.6 -> To Version 10.0.0-beta.25609.2
…211.1

On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 10.0.0-beta.25555.6 -> To Version 10.0.0-beta.25611.1
@github-project-automation github-project-automation bot moved this from New to In Progress in F# Compiler and Tooling Dec 12, 2025
@T-Gro T-Gro enabled auto-merge (squash) December 12, 2025 08:24
@T-Gro T-Gro merged commit 09ded38 into release/dev18.0 Dec 12, 2025
40 of 41 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in F# Compiler and Tooling Dec 12, 2025
@dotnet-maestro dotnet-maestro bot deleted the darc-release/dev18.0-1e137a07-f7df-4e80-b278-aa45a4e297e4 branch December 12, 2025 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants