chore(deps): update microsoft.aspnetcore to 10.0.8

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.AspNetCore.Authentication.JwtBearer (source)	nuget	patch	10.0.7 → 10.0.8
Microsoft.AspNetCore.Mvc.Testing (source)	nuget	patch	10.0.7 → 10.0.8
Microsoft.AspNetCore.OpenApi (source)	nuget	patch	10.0.7 → 10.0.8
Microsoft.AspNetCore.TestHost (source)	nuget	patch	10.0.7 → 10.0.8

---

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 Mend Renovate.

[claude]

Review: Routine ASP.NET Core Patch Update (10.0.7 → 10.0.8)

Overall: LGTM — clean, consistent patch bump.

What this PR does

Renovate bot bumps four Microsoft.AspNetCore packages from 10.0.7 to 10.0.8 across all relevant project files:

• Microsoft.AspNetCore.Authentication.JwtBearer
• Microsoft.AspNetCore.Mvc.Testing
• Microsoft.AspNetCore.OpenApi
• Microsoft.AspNetCore.TestHost

Observations

Central Package Management is handled correctly. Directory.Packages.props is updated as the source of truth, and the per-project PackageReference Version attributes in TUnit.AspNetCore.Core and TUnit.AspNetCore.Tests are kept in sync — these exist for CPM tracking, while the actual resolved version for net8.0/net9.0 targets is controlled via VersionOverride (8.0.0 / 9.0.0 respectively), which is untouched and correct.

All affected locations are updated consistently — main props file, library project, test project, templates (both C# and F#), and the CloudShop example. No file was missed.

Template projects pin to a specific version rather than a floating range, which is reasonable here since they're part of the TUnit repo and not distributed as standalone starters with their own update cadence.

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

[claude]

Review: Routine ASP.NET Core Patch Update (10.0.7 → 10.0.8)

LGTM — no issues found. Previous approval stands.

This is a Renovate-generated patch bump for four Microsoft.AspNetCore packages across 7 files. The changes are mechanically correct and consistent.

Checklist

• Central Package Management: Directory.Packages.props updated as the authoritative source of truth.
• Per-project overrides intact: VersionOverride values for net8.0 (→ 8.0.0) and net9.0 (→ 9.0.0) in TUnit.AspNetCore.Core and TUnit.AspNetCore.Tests are correctly left unchanged — only the CPM tracking Version attribute is bumped.
• All locations updated: library project, test project, both templates (C# and F#), WebApp example, and CloudShop example — nothing missed.
• No logic changes: purely a version string update; no risk of behavioral regression.

Automerge is enabled and this is safe to merge.