chore(deps): update microsoft.extensions to 10.0.6

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.Extensions.DependencyInjection (source)	nuget	patch	10.0.5 → 10.0.6
Microsoft.Extensions.Logging (source)	nuget	patch	10.0.5 → 10.0.6
Microsoft.Extensions.Logging.Abstractions (source)	nuget	patch	10.0.5 → 10.0.6

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[azure-pipelines]

Azure Pipelines:
1 pipeline(s) were filtered out due to trigger conditions.

[claude]

Code Review: chore(deps): update microsoft.extensions to 10.0.6

This is a Renovate-generated dependency update PR bumping three Microsoft.Extensions packages from 10.0.5 → 10.0.6 (patch release).

Summary

The changes are clean and consistent — four files updated, all mechanical version bumps with no logic changes.

Observations

Directory.Packages.props — Correct. Central Package Management (CPM) is the right place to pin versions for these transitive dependencies.

TUnit.Logging.Microsoft and TUnit.Mocks.Logging project files — These update the Version attribute alongside VersionOverride:

<PackageReference Include="Microsoft.Extensions.Logging" Version="10.0.6" VersionOverride="8.0.0" />

This is a pre-existing pattern worth noting: when VersionOverride is present in CPM, it is the effective resolved version — VersionOverride="8.0.0" is what actually gets used for net8.0 targets. The Version attribute here is redundant and effectively ignored. Renovate updates it anyway because it matches its version-bump heuristic. This isn't a regression introduced by this PR, but if these files were cleaned up to remove the extraneous Version attribute, Renovate would stop generating noisy duplicate version changes in these project files on each update.

TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj — Correct. Template projects intentionally carry explicit versions because they are meant to be standalone artifacts, outside of the solution's CPM scope.

Verdict

No issues. This is a safe, low-risk patch update. The changes follow the existing conventions in the repo correctly. The Renovate configuration is working as intended.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}