chore(deps): update microsoft.extensions to 10.0.7

[thomhurst]

This PR contains the following updates:

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

---

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.

[claude]

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

This is a routine patch-level dependency bump from Renovate Bot, updating three Microsoft.Extensions packages from 10.0.6 → 10.0.7.

Summary of changes

File	What changed
Directory.Packages.props	Central Package Management (CPM) version bumped for all three packages
TUnit.Logging.Microsoft/TUnit.Logging.Microsoft.csproj	Per-TFM Version attribute updated (net8.0 / net9.0 overrides)
TUnit.Mocks.Logging/TUnit.Mocks.Logging.csproj	Same as above for Logging.Abstractions
TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj	Inline version updated in the F# template

Assessment

No issues found. The change is correct and consistent:

• All three packages are bumped in lock-step, which is expected since they ship together and share a version scheme.
• The CPM file is the authoritative source for net10.0 targets; the per-TFM VersionOverride in TUnit.Logging.Microsoft and TUnit.Mocks.Logging correctly pins older TFM targets to their framework-matching versions (8.0.0 / 9.0.0), so those are unaffected at runtime.
• The template project uses an inline version (no CPM), which is intentional for standalone template projects — this update keeps it consistent with the rest of the repo.

Minor observation (not blocking)

In TUnit.Logging.Microsoft.csproj and TUnit.Mocks.Logging.csproj, the Version attribute on the per-TFM PackageReference items (e.g. Version="10.0.7" VersionOverride="8.0.0") is technically redundant because VersionOverride takes precedence for those targets. The Version value is only meaningful for net10.0, where it mirrors the CPM entry. This was pre-existing before this PR and has no functional impact — just worth being aware of.

Approved — safe to merge.

[claude]

Routine patch bump — no issues found. Safe to merge.

[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

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes. Give us feedback}

[claude]

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

Routine patch-level dependency bump generated by Renovate Bot — → for three packages that ship together:

• Microsoft.Extensions.DependencyInjection
• Microsoft.Extensions.Logging
• Microsoft.Extensions.Logging.Abstractions

Changes reviewed

File	Change
Directory.Packages.props	Central Package Management (CPM) versions bumped
TUnit.Logging.Microsoft/TUnit.Logging.Microsoft.csproj	Per-TFM Version attribute updated for net8.0 / net9.0 override entries
TUnit.Mocks.Logging/TUnit.Mocks.Logging.csproj	Same for Logging.Abstractions
TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj	Inline version updated in the standalone F# template

Assessment

No issues found. The update is correct and consistent:

• All three packages are bumped in lock-step, which is expected — they share a version scheme and release together.
• The per-TFM VersionOverride attributes in TUnit.Logging.Microsoft and TUnit.Mocks.Logging correctly pin older TFM targets (net8.0 → 8.0.0, net9.0 → 9.0.0), so those remain unaffected at runtime.
• The F# template uses an inline version rather than CPM (intentional for standalone templates), and this PR keeps it aligned with the rest of the repo.

Safe to merge.

[claude]

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

Routine patch-level dependency bump generated by Renovate Bot — packages bumped from version 10.0.6 to 10.0.7:

• Microsoft.Extensions.DependencyInjection
• Microsoft.Extensions.Logging
• Microsoft.Extensions.Logging.Abstractions

Changes reviewed

File	Change
Directory.Packages.props	Central Package Management (CPM) versions bumped
TUnit.Logging.Microsoft/TUnit.Logging.Microsoft.csproj	Per-TFM Version attribute updated for net8.0/net9.0 override entries
TUnit.Mocks.Logging/TUnit.Mocks.Logging.csproj	Same for Logging.Abstractions
TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj	Inline version updated in the standalone F# template

Assessment

No issues found. The update is correct and consistent:

• All three packages are bumped in lock-step, which is expected as they share a version scheme and release together.
• The per-TFM VersionOverride attributes in TUnit.Logging.Microsoft and TUnit.Mocks.Logging correctly pin older TFM targets (net8.0 to 8.0.0, net9.0 to 9.0.0), so those remain unaffected at runtime.
• The F# template uses an inline version rather than CPM (intentional for standalone templates), and this PR keeps it aligned with the rest of the repo.

Safe to merge.