Skip to content

Conversation

@hikarisakamoto
Copy link

From the Contributing Guidelines:

  • [] If adding a new feature, I discussed it's design in an issue first
  • I verified there are no code warnings emitted for my code
  • I've included a unit test, and all the unit tests are passing

Title

Update to .NET 10 and refresh dependencies

Description

Align the solution with .NET 10, refresh Roslyn/NuGet/test dependencies, and expand coverage for locating the .NET 10 runtime/reference packs.

Changes Made

1. Updated to .NET 10

Switched all projects and test assets to target net10.0
Added global.json to pin SDK 10 and keep roll-forward behavior

2. Updated NuGet packages

Bumped Roslyn, NuGet client packages, Spectre.Console, System.* libraries, and OpenAI to current net10-compatible versions
Updated test dependencies (xUnit, coverlet, Spectre.Console.Testing, System.IO.Abstractions.TestingHelpers)
Added net10 runtime locator tests for global installs and NuGet fallbacks; updated evaluation/source-link expectations

Why These Changes?

.NET 10: Keep the project current with the latest SDK/runtime and

@waf
Copy link
Owner

waf commented Nov 26, 2025

Thank you! This looks great. I will get this merged/released later today.

<PackageReference Include="Spectre.Console.Cli" Version="0.49.1" />
<PackageReference Include="System.IO.Abstractions" Version="21.1.3" />
<PackageReference Include="System.Configuration.ConfigurationManager" Version="9.0.0" />
<PackageReference Include="Spectre.Console.Cli" Version="0.53.0" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a hotfix version later this version

Suggested change
<PackageReference Include="Spectre.Console.Cli" Version="0.53.0" />
<PackageReference Include="Spectre.Console.Cli" Version="0.53.1" />


<ItemGroup>
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.11.1" />
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.0.1" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.0.1" />
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.0.1" />


<ItemGroup>
<PackageReference Include="PrettyPrompt" Version="4.1.1" />
<PackageReference Include="System.CommandLine" Version="2.0.0-beta4.22272.1" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe could move to the stable version, but may need to handle some breaking changes

Suggested change
<PackageReference Include="System.CommandLine" Version="2.0.0-beta4.22272.1" />
<PackageReference Include="System.CommandLine" Version="2.0.0" />

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I was looking into that... Although I managed to run it, many tests broke and I started to look into them to see exactly what needed to be updated... Might take some time

@hikarisakamoto
Copy link
Author

hikarisakamoto commented Nov 26, 2025

I will be out for the rest of the week, but I can look as soon as I get back, on why the build broke

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.

3 participants