chore(deps): update dependency microsoft.entityframeworkcore to 10.0.6

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.EntityFrameworkCore (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 this update 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: PR #5542 — Update Microsoft.EntityFrameworkCore to 10.0.6

Summary: This is a fully automated patch-level dependency bump generated by Renovate Bot, updating Microsoft.EntityFrameworkCore from 10.0.5 to 10.0.6 in Directory.Packages.props.

---

Change Analysis

What changed: The PackageVersion entry for Microsoft.EntityFrameworkCore in the central package management file (Directory.Packages.props) is bumped from 10.0.5 to 10.0.6.

Scope of impact: EF Core is only consumed by the TUnit.Example.Asp.Net sample project, not by any core TUnit library or test infrastructure. This means the bump carries no risk to the testing framework itself.

Correctness: The change is correct. Central Package Management (CPM) is properly used — the version is updated in Directory.Packages.props and the consuming project already has a versionless <PackageReference Include="Microsoft.EntityFrameworkCore" />.

---

Findings

No issues found. Specifically:

• This is a patch release (10.0.5 → 10.0.6). EF Core follows SemVer; patch releases contain only bug fixes and are backward-compatible.
• The package is only used in the sample/example project, not in any TUnit core, engine, or source-generator project. There is zero risk of test framework regressions.
• The Microsoft.Extensions.* family (DI, Logging) remains at 10.0.5 — this asymmetry is normal and expected since EF Core has its own release cadence.
• No snapshot test changes, no public API surface changes, no source generator changes — the TUnit snapshot testing requirement is not triggered.

---

Verdict

✅ Approve and merge. This is a safe, low-risk automated patch bump with no design, architectural, or correctness concerns. The auto-merge configuration is appropriate for this type of change.

[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}