chore: bump to .NET 10 (LTS)#14
Merged
Merged
Conversation
- EftViewer.Desktop: net8.0 -> net10.0 (.NET 8 LTS EOL Nov 2026) - EftViewer.Core.Tests: net9.0 -> net10.0 (.NET 9 STS already EOL ~May 2026) - build.yml + release.yml: setup-dotnet 8.0.x -> 10.0.x - README: .NET 8 references -> .NET 10 - EftViewer.Core stays netstandard2.0 (deliberate max-compat consumption target) Moves both runnable projects to the current LTS (supported to ~Nov 2028) and off the already-out-of-support net9 the tests were pinned to. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Move both runnable projects to .NET 10 (LTS) and update docs/workflows.
EftViewer.Desktopnet8.0net10.0EftViewer.Core.Testsnet9.0net10.0EftViewer.Corenetstandard2.0Also:
build.yml+release.ymlsetup-dotnet8.0.x → 10.0.x, and the.NET 8mentions in the README →.NET 10.Why
Verification
This is mechanical, but the proof is CI:
build.ymlcompiles the solution and runs the xUnit suite on net10 against this PR. Green check = verified.Risk
The one thing that could break: Avalonia is pinned at
11.3.11— it should support net10 (11.3.x post-dates the Nov 2025 net10 RTM), but if CI flags it, the fix is a bump to the latest Avalonia 11.x. Will update here if the check goes red.🤖 Generated with Claude Code