chore(deps): update tunit to 1.18.9

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.18.0 → 1.18.9
TUnit.AspNetCore	nuget	patch	1.18.0 → 1.18.9
TUnit.Assertions	nuget	patch	1.18.0 → 1.18.9
TUnit.Assertions.FSharp	nuget	patch	1.18.0 → 1.18.9
TUnit.Core	nuget	patch	1.18.0 → 1.18.9
TUnit.Engine	nuget	patch	1.18.0 → 1.18.9
TUnit.Playwright	nuget	patch	1.18.0 → 1.18.9

---

Release Notes

thomhurst/TUnit (TUnit)

v1.18.9: 1.18.9

What's Changed

Other Changes

• perf: reduce source-gen JIT overhead via metadata factory helpers by @​thomhurst in #​5056
• perf: add ParameterMetadataFactory and lazy ReflectionInfo resolution by @​thomhurst in #​5057
• feat: distributed trace collection for HTML report by @​thomhurst in #​5059

Dependencies

• chore(deps): update tunit to 1.18.0 by @​thomhurst in #​5052
• chore(deps): update docker/setup-docker-action action to v5 by @​thomhurst in #​5058

Full Changelog: v1.18.0...v1.18.9

---

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: chore(deps): update tunit to 1.18.9

This is a straightforward Renovate Bot dependency update bumping all TUnit-family packages from 1.18.0 → 1.18.9 (patch version bump).

Summary of Changes

• Directory.Packages.props: 6 TUnit package versions updated centrally
• TUnit.Templates/: 5 template project files updated to match

Review Notes

No issues found. This is a clean, mechanical patch version bump.

A few observations worth noting:

1. Centralized version management is well-structured: The Directory.Packages.props correctly acts as the single source of truth for the main repo packages. However, the template project files under TUnit.Templates/content/ pin their own versions independently (not referencing Directory.Packages.props), which is intentional for templates — they need to be self-contained starters for end users.

2. Version consistency: All TUnit packages are correctly bumped to the same 1.18.9 patch version, maintaining coherent versioning across the ecosystem (TUnit, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Playwright).

3. Patch version scope: Given that 1.18.9 includes performance improvements (JIT overhead reduction, lazy ReflectionInfo resolution) and a new distributed trace collection feature for HTML reports from the release notes, upgrading templates to the latest patch is appropriate so new users scaffolded from templates get the best-performing version out of the box.

Verdict

Approve. This is a safe, well-formed dependency update with no architectural or code concerns.