chore: use .NET10 only

[arika0093]

This pull request updates the project's .NET version support and streamlines related configuration files. The main focus is to standardize on .NET 10.0 for builds, tests, and examples, while cleaning up obsolete or redundant settings.

.NET Version Standardization:

• Updated the dev container to only include .NET 10.0 as an additional version, removing support for 8.0 and 6.0 (.devcontainer/devcontainer.json).
• Changed the GitHub Actions workflow to use only .NET 10.0, setting DOTNET_VERSION to 10.0.x and updating the setup step to reference this environment variable (.github/workflows/test.yaml). [1] [2]

Project and Test Configuration:

• Updated examples/Directory.Build.props to explicitly target net10.0.
• Removed explicit TargetFramework settings from individual example project files, relying on the shared props file instead (Linqraft.ApiSample.csproj, Linqraft.Benchmark.csproj, Linqraft.MinimumSample.csproj, Linqraft.Sample.csproj). [1] [2] [3] [4]
• Simplified test project configuration to default to net10.0 unless overridden, and removed legacy multi-targeting and Windows-specific settings (tests/Directory.Build.props).
• Removed the unused Newtonsoft.Json package reference from test dependencies (tests/Directory.Build.props).
• Removed explicit TargetFrameworks property from Linqraft.Analyzer.Tests.csproj to rely on the shared configuration.

Summary by CodeRabbit

• Chores
  • Consolidated .NET version support to 10.0 across development and testing environments.
  • Simplified CI/CD workflow configuration by centralizing version management through environment variables.
  • Centralized target framework configuration for example projects via shared build properties.
  • Removed Newtonsoft.Json dependency from test suite.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The pull request consolidates .NET 10.0 targeting across the project by updating devcontainer configuration to support only .NET 10.0, introducing dotnet version environment variables in CI workflows, centralizing target framework definitions in Directory.Build.props files, and removing explicit TargetFramework entries from individual project files to inherit from build props instead.

Changes

Cohort / File(s)	Summary
Dev & CI Configuration .devcontainer/devcontainer.json, .github/workflows/test.yaml	Reduces devcontainer supported .NET versions from "10.0, 8.0, 6.0" to "10.0"; introduces DOTNET_VERSION workflow environment variable and replaces hard-coded multi-version list with environment variable reference in Setup .NET step
Build Props (Framework Defaults) examples/Directory.Build.props, tests/Directory.Build.props	Adds net10.0 target framework to examples build props; updates tests build props to use conditional $(TFMS) variable (defaulting to net10.0) and removes Newtonsoft.Json package reference
Example Projects (TargetFramework Removal) examples/Linqraft.ApiSample/Linqraft.ApiSample.csproj, examples/Linqraft.Benchmark/Linqraft.Benchmark.csproj, examples/Linqraft.MinimumSample/Linqraft.MinimumSample.csproj, examples/Linqraft.Sample/Linqraft.Sample.csproj	Removes explicit net10.0 TargetFramework entries from each project, allowing inheritance from centralized Directory.Build.props
Test Projects (TargetFrameworks Removal) tests/Linqraft.Analyzer.Tests/Linqraft.Analyzer.Tests.csproj	Removes explicit TargetFrameworks element, allowing inheritance from centralized tests/Directory.Build.props configuration

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Areas for attention:
  • Verify that all example and test projects correctly inherit the net10.0 target framework from their respective Directory.Build.props files
  • Confirm that the $(TFMS) conditional in tests/Directory.Build.props properly defaults to net10.0 when the environment variable is not set
  • Ensure CI workflow correctly references env.DOTNET_VERSION and that the environment variable is properly defined at the workflow level

Possibly related PRs

• PR #20: Modifies CI dotnet version configuration and updates project target frameworks to .NET 10, indicating directly overlapping framework consolidation efforts.
• PR #25: Updates build configuration and Directory.Build.props with framework targeting changes, showing related build system modifications.

Poem

🐰 A rabbit hops through .NET ten,
Consolidating frameworks then and when,
No six or eight need apply today,
Just ten will point the hoppy way! 🎯
Build props now reign, from props we've thinned,
Configuration unified and pinned.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: use .NET10 only' is clear, concise, and directly captures the main objective: standardizing the repository to use only .NET 10.0, which is the primary change reflected across all modified files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/use-only-dotnet10

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/test.yaml (1)

41-42: Consider adding dotnet clean before build to avoid stale generator caches.

Based on learnings, this project requires a clean build to avoid stale generator caches. The current build step does not include a clean phase. While CI workflows often skip clean for performance, the learnings explicitly recommend: dotnet clean && dotnet build --no-incremental.

Can you confirm whether this is a pre-existing gap in the workflow, or if a clean build should be included as part of this PR? If needed, apply this diff:

       - name: Build
-        run: dotnet build --no-restore
+        run: dotnet clean && dotnet build --no-restore

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 00284a7 and 3b116e4.

📒 Files selected for processing (9)

• .devcontainer/devcontainer.json (1 hunks)
• .github/workflows/test.yaml (2 hunks)
• examples/Directory.Build.props (1 hunks)
• examples/Linqraft.ApiSample/Linqraft.ApiSample.csproj (0 hunks)
• examples/Linqraft.Benchmark/Linqraft.Benchmark.csproj (0 hunks)
• examples/Linqraft.MinimumSample/Linqraft.MinimumSample.csproj (0 hunks)
• examples/Linqraft.Sample/Linqraft.Sample.csproj (0 hunks)
• tests/Directory.Build.props (1 hunks)
• tests/Linqraft.Analyzer.Tests/Linqraft.Analyzer.Tests.csproj (0 hunks)

💤 Files with no reviewable changes (5)

• examples/Linqraft.Benchmark/Linqraft.Benchmark.csproj
• examples/Linqraft.ApiSample/Linqraft.ApiSample.csproj
• examples/Linqraft.Sample/Linqraft.Sample.csproj
• examples/Linqraft.MinimumSample/Linqraft.MinimumSample.csproj
• tests/Linqraft.Analyzer.Tests/Linqraft.Analyzer.Tests.csproj

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-11-25T12:08:35.836Z

Learnt from: CR
Repo: arika0093/Linqraft PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-25T12:08:35.836Z
Learning: Always perform a clean build to avoid stale generator caches; run: `dotnet clean && dotnet build --no-incremental`

Applied to files:

• .github/workflows/test.yaml

🔇 Additional comments (4)

.github/workflows/test.yaml (1)

14-15: Environment variable consolidation aligns well with PR objectives.

Introducing DOTNET_VERSION as a centralized environment variable and replacing the hard-coded version list with a reference to it is a clean approach. This eliminates maintenance friction when the target version needs to be updated in the future.

Also applies to: 34-34

.devcontainer/devcontainer.json (1)

12-12: Devcontainer now aligned to .NET 10 only

Using "additionalVersions": "10.0" matches the repo’s move to .NET 10; just make sure the devcontainers dotnet feature currently provides a 10.0 install so container creation doesn’t break.

examples/Directory.Build.props (1)

3-3: Centralized example TFM on net10.0

Setting <TargetFramework>net10.0</TargetFramework> here is a good centralization and lines up with the repo’s single-TFM strategy; just ensure local/CI SDKs are new enough to understand net10.0.

tests/Directory.Build.props (1)

3-4: TFMS-based test targeting with net10.0 default looks solid

The conditional <TargetFrameworks> setup (TFMS override, net10.0 fallback) is a clean way to keep multi-targeting flexibility while standardizing on .NET 10; just confirm individual test projects aren’t redefining TargetFramework/TargetFrameworks in a conflicting way.