chore(deps): update microsoft.aspnetcore to 10.0.6

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.AspNetCore.Authentication.JwtBearer (source)	nuget	patch	10.0.5 → 10.0.6
Microsoft.AspNetCore.Mvc.Testing (source)	nuget	patch	10.0.5 → 10.0.6
Microsoft.AspNetCore.OpenApi (source)	nuget	patch	10.0.5 → 10.0.6
Microsoft.AspNetCore.TestHost (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.aspnetcore to 10.0.6

This is a straightforward Renovate Bot patch update bumping 4 Microsoft.AspNetCore packages from 10.0.5 → 10.0.6 across 7 files. The changes are purely version string replacements — no logic is touched.

What looks good

• All 4 packages are updated to the same patch version consistently.
• The VersionOverride values in TUnit.AspNetCore.Core and TUnit.AspNetCore.Tests are correctly not updated — those TFM-specific overrides (8.0.0, 9.0.0) are intentional pins for framework compatibility and should stay as-is.
• Central Package Management (Directory.Packages.props) is the authoritative source and is updated correctly.

Minor architectural observation (pre-existing, not introduced here)

Template projects (TUnit.Templates/) and the CloudShop example use inline Version attributes rather than deferring to CPM. This means Renovate must update them independently from the main CPM entry, which it does correctly here. It's a known trade-off for standalone/distributable templates and examples, but worth noting that these are a potential drift risk if Renovate ever misses them.

Verdict

No issues with this PR. The update is safe to merge as-is, and auto-merge is appropriately enabled for this patch-level dependency bump.

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