chore(deps): update tunit to 1.24.18

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.24.13 → 1.24.18
TUnit.AspNetCore	nuget	patch	1.24.13 → 1.24.18
TUnit.Assertions	nuget	patch	1.24.13 → 1.24.18
TUnit.Assertions.FSharp	nuget	patch	1.24.13 → 1.24.18
TUnit.Core	nuget	patch	1.24.13 → 1.24.18
TUnit.Engine	nuget	patch	1.24.13 → 1.24.18
TUnit.Playwright	nuget	patch	1.24.13 → 1.24.18

---

Release Notes

thomhurst/TUnit (TUnit)

v1.24.18: 1.24.18

What's Changed

Other Changes

• feat(mocks): shorter, more readable generated mock type names by @​thomhurst in #​5334
• Fix DisposeAsync() ordering for nested property injection by @​Copilot in #​5337

Dependencies

• chore(deps): update tunit to 1.24.13 by @​thomhurst in #​5331

Full Changelog: v1.24.13...v1.24.18

---

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]

Dependency Update Review: TUnit packages 1.24.13 → 1.24.18

This is a straightforward automated patch bump from Renovate Bot, updating all TUnit-family packages across the monorepo from 1.24.13 to 1.24.18.

What changed:

• Directory.Packages.props — central version pins for TUnit, TUnit.Assertions, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, and TUnit.Assertions.FSharp
• Template project files (TUnit.Templates/content/*) — each template's hardcoded PackageReference versions bumped in lockstep

Observations:

1. Consistency is correct. All seven package references have been updated together to the same patch version, which is the right approach since these packages are tightly coupled within the monorepo.

2. Template project files are hardcoded versions. The template .csproj/.fsproj files in TUnit.Templates/content/ use explicit version strings rather than inheriting from Directory.Packages.props. This is intentional for templates (they serve as standalone starting points for users), but it means every release requires touching both the central props file and each template individually. This is working as expected and Renovate handles it automatically, so no action needed — just worth noting as the expected maintenance cost of the template approach.

3. Release notes for v1.24.18 include:

   • Shorter, more readable generated mock type names (#5334)
   • Fix for DisposeAsync() ordering for nested property injection (#5337)

   Both are reasonable inclusions in a patch release. The disposal ordering fix in particular is a correctness improvement that warrants picking up promptly.

4. Auto-merge is enabled, which is appropriate for a Renovate-managed patch update with no API or behavior changes.

No issues found. The change is mechanical, correct, and 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

_{TIP This summary will be updated as you push new changes. Give us feedback}