chore(deps): update tunit to 1.17.11

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.17.7 → 1.17.11
TUnit.AspNetCore	nuget	patch	1.17.7 → 1.17.11
TUnit.Assertions	nuget	patch	1.17.7 → 1.17.11
TUnit.Assertions.FSharp	nuget	patch	1.17.7 → 1.17.11
TUnit.Core	nuget	patch	1.17.7 → 1.17.11
TUnit.Engine	nuget	patch	1.17.7 → 1.17.11
TUnit.Playwright	nuget	patch	1.17.7 → 1.17.11

---

Release Notes

thomhurst/TUnit (TUnit)

v1.17.11: 1.17.11

What's Changed

Other Changes

• chore: migrate from .sln to .slnx solution format by @​thomhurst in #​4984
• feat(mocks): unified Mock API — remove Setup/Verify/Raise surfaces by @​thomhurst in #​4991

Dependencies

• chore(deps): update tunit to 1.17.7 by @​thomhurst in #​4983

Full Changelog: v1.17.7...v1.17.11

---

Configuration

📅 Schedule: 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: Dependency Update (1.17.7 → 1.17.11)

This is a Renovate-generated patch bump across all TUnit packages. The changes are straightforward and mechanical.

What's Included in 1.17.11

Per the release notes, this update bundles:

• Migration from .sln to .slnx solution format
• Unified Mock<T> API (removal of Setup/Verify/Raise surfaces)

Review of Changes

Consistency: All 7 packages are updated uniformly to 1.17.11 — no version mismatches introduced. Good.

Two sources of truth for template versions: The template project files under TUnit.Templates/content/ carry hardcoded version numbers separately from Directory.Packages.props. This is intentional (templates need explicit pinned versions for scaffolding), and this PR correctly updates both places in sync.

TUnit.Playwright gap in central management: TUnit.Playwright is only updated in the template TestProject.csproj, not in Directory.Packages.props. This appears to be by design — if no non-template project in the solution consumes TUnit.Playwright, it doesn't need a central entry. Worth verifying this remains true as the project grows, to avoid version drift.

Verdict

No issues. Clean, consistent bump. Safe to merge.