chore(deps): update tunit to 1.22.19

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.22.6 → 1.22.19
TUnit.AspNetCore	nuget	patch	1.22.6 → 1.22.19
TUnit.Assertions	nuget	patch	1.22.6 → 1.22.19
TUnit.Assertions.FSharp	nuget	patch	1.22.6 → 1.22.19
TUnit.Core	nuget	patch	1.22.6 → 1.22.19
TUnit.Engine	nuget	patch	1.22.6 → 1.22.19
TUnit.Playwright	nuget	patch	1.22.6 → 1.22.19

---

Release Notes

thomhurst/TUnit (TUnit)

v1.22.19: 1.22.19

What's Changed

Other Changes

• Add mock library benchmarks: TUnit.Mocks vs Moq, NSubstitute, FakeItEasy by @​Copilot in #​5284
• perf: lazily initialize optional MockEngine collections by @​thomhurst in #​5289
• Always emit TUnit.Mocks.Generated namespace from source generator by @​Copilot in #​5282

Dependencies

• chore(deps): update tunit to 1.22.6 by @​thomhurst in #​5285

Full Changelog: v1.22.6...v1.22.19

---

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

Summary: This is a Renovate Bot-generated dependency update bumping all TUnit-family packages from 1.22.6 to 1.22.19 (a patch release). The changes are purely mechanical version bumps across 6 files.

Assessment: ✅ Looks good

What's changed:

• Directory.Packages.props — central version management updated for 7 TUnit packages
• 5 project templates in TUnit.Templates/ updated to reference the new version

What I checked:

• All TUnit-related packages are consistently bumped to 1.22.19 — no version mismatches between packages
• Template projects and the central Directory.Packages.props are in sync
• The TUnit.Playwright package in its template is updated, which is appropriate since it's a separate package from the main TUnit umbrella
• No TUnit package versions were inadvertently skipped or left behind

One observation (not a blocker):
The template project files (e.g. TUnit.AspNet.FSharp, TUnit.FSharp) hardcode explicit package versions rather than using the central Directory.Packages.props via <PackageVersion>. This means template consumers always get the version baked in at template-generation time, which is actually desirable for templates (users get a known-good starting point). However, it does mean two places need updating per release (central props + each template). This is an existing pattern — not something introduced by this PR — so no action needed here.

This PR is a clean, automerge-eligible patch dependency update with no concerns.

[claude]

Code Review: chore(deps): update tunit to 1.22.19

This is a Renovate Bot-generated dependency update bumping all TUnit-family packages from 1.22.6 to 1.22.19 (a patch release). The changes are purely mechanical version bumps across 6 files.

Assessment: LGTM

What's changed:

• Directory.Packages.props — central version management updated for 7 TUnit packages
• 5 project templates in TUnit.Templates/ updated to reference the new version

What I verified:

• All TUnit-related packages are consistently bumped to 1.22.19 — no version mismatches
• Template projects and the central Directory.Packages.props are in sync
• No packages were inadvertently left at the old version

Regarding the release notes for v1.22.19:

The changes included in this patch bump are:

1. Mock library benchmarks (TUnit.Mocks vs Moq, NSubstitute, FakeItEasy) — additive, no breaking changes
2. perf: lazily initialize optional MockEngine collections — a targeted performance improvement, safe to consume
3. Always emit TUnit.Mocks.Generated namespace from source generator — a correctness fix for the Mocks source generator

None of these introduce API changes or risky behavioral changes. The lazy initialization of MockEngine collections (#5289) is a pure optimization with no observable side effects.

Previous review comment status:

The previous review noted that template project files hardcode explicit package versions rather than centralizing via Directory.Packages.props. This is an existing architectural pattern (not introduced by this PR), and remains the same here — templates intentionally bake in a known-good version for users who scaffold from them. No action needed.

This PR is safe to merge as-is. The automerge configuration looks correct for this kind of routine patch update.