chore(deps): update microsoft.aspnetcore to 10.0.7

[thomhurst]

This PR contains the following updates:

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

This is a clean, automated Renovate Bot patch-version bump for four Microsoft.AspNetCore packages: 10.0.6 → 10.0.7.

Summary

The change is correct and complete — all references to these packages across the repository have been updated consistently:

• Central Package Management (Directory.Packages.props)
• TUnit.AspNetCore.Core and TUnit.AspNetCore.Tests (TFM-conditional overrides)
• Template projects (TUnit.AspNet, TUnit.AspNet.FSharp)
• Example project (CloudShop.ApiService)

No issues found with the changes themselves.

Observation (pre-existing, not introduced by this PR)

The template and example projects use direct PackageReference version pins rather than Central Package Management. This means they require separate updates (as this PR correctly does), but it also means they can drift silently if a future bump only touches Directory.Packages.props. This is a reasonable trade-off for templates (which are scaffolded independently), but worth noting if these templates are expected to stay in sync with the main project's dependency versions.

Verdict

Approved. Routine patch update, no regressions expected, all locations updated consistently. Safe to merge.

[claude]

Code Review

This is a clean, automated Renovate Bot patch-version bump for four Microsoft.AspNetCore packages: 10.0.6 → 10.0.7.

Summary

The change is correct and complete — all references to these packages across the repository have been updated consistently:

• Central Package Management (Directory.Packages.props)
• TUnit.AspNetCore.Core and TUnit.AspNetCore.Tests (TFM-conditional overrides)
• Template projects (TUnit.AspNet, TUnit.AspNet.FSharp)
• Example project (CloudShop.ApiService)

No issues found with the changes themselves.

Observation (pre-existing, not introduced by this PR)

The template and example projects use direct PackageReference version pins rather than Central Package Management. This means they require separate updates (as this PR correctly does), but it also means they can drift silently if a future bump only touches Directory.Packages.props. This is a reasonable trade-off for templates (which are scaffolded independently), but worth noting if these templates are expected to stay in sync with the main project's dependency versions.

Verdict

Approved. Routine patch update, no regressions expected, all locations updated consistently. Safe to merge.

[codacy-production]

Up to standards ✅

🟢 Issues0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics0 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}