chore(deps): update tunit to 1.22.3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.22.0 → 1.22.3
TUnit.AspNetCore	nuget	patch	1.22.0 → 1.22.3
TUnit.Assertions	nuget	patch	1.22.0 → 1.22.3
TUnit.Assertions.FSharp	nuget	patch	1.22.0 → 1.22.3
TUnit.Core	nuget	patch	1.22.0 → 1.22.3
TUnit.Engine	nuget	patch	1.22.0 → 1.22.3
TUnit.Playwright	nuget	patch	1.22.0 → 1.22.3

---

Release Notes

thomhurst/TUnit (TUnit)

v1.22.3: 1.22.3

What's Changed

Other Changes

• fix: pass assembly version properties to dotnet pack by @​thomhurst in #​5274

Dependencies

• chore(deps): update tunit to 1.22.0 by @​thomhurst in #​5272

Full Changelog: v1.22.0...v1.22.3

---

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

This is a straightforward Renovate-generated dependency bump PR updating all TUnit-family packages from 1.22.0 → 1.22.3 across 6 files.

Summary of Changes

• Directory.Packages.props — Central package management updated for 6 TUnit packages (TUnit, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.AspNetCore, TUnit.Core, TUnit.Engine)
• TUnit.Templates/ — Template project files updated for TUnit, TUnit.Assertions.FSharp, and TUnit.Playwright packages

Assessment

No issues found. The change is mechanically correct:

• All 7 TUnit-family packages are consistently bumped to the same 1.22.3 patch version — no version skew between related packages.
• The Directory.Packages.props central version management approach is respected — the template .csproj/.fsproj files that have hardcoded versions (outside CPM) are also updated correctly.
• v1.22.3 is a known-good release, with a single fix: "pass assembly version properties to dotnet pack" (#5274) — a safe patch to pull in.
• No snapshot tests, source generator output, or public APIs are touched, so no .verified.txt regeneration is needed.

One Observation (Non-blocking)

The template files under TUnit.Templates/content/ still carry hardcoded version strings rather than referencing a variable or the central Directory.Packages.props. This means each dependency bump requires updating both places. This is likely intentional (templates ship as standalone projects), but it's worth noting that a $(TUnitVersion) MSBuild property set at the repo level could simplify future bumps. Not a concern for this PR.

✅ Safe to merge.

[claude]

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

This is a straightforward Renovate-generated dependency bump PR updating all TUnit-family packages from 1.22.0 → 1.22.3 across 6 files.

Summary of Changes

• Directory.Packages.props — Central package management updated for 6 TUnit packages (TUnit, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.AspNetCore, TUnit.Core, TUnit.Engine)
• TUnit.Templates/ — Template project files updated for TUnit, TUnit.Assertions.FSharp, and TUnit.Playwright packages

Assessment

No issues found. The change is mechanically correct:

• All 7 TUnit-family packages are consistently bumped to the same 1.22.3 patch version — no version skew between related packages.
• The Directory.Packages.props central version management approach is respected — the template .csproj/.fsproj files that have hardcoded versions (outside CPM) are also updated correctly.
• v1.22.3 is a known-good release, with a single fix: "pass assembly version properties to dotnet pack" (#5274) — a safe patch to pull in.
• No snapshot tests, source generator output, or public APIs are touched, so no .verified.txt regeneration is needed.

One Observation (Non-blocking)

The template files under TUnit.Templates/content/ still carry hardcoded version strings rather than referencing a variable or the central Directory.Packages.props. This means each dependency bump requires updating both places. This is likely intentional (templates ship as standalone projects), but it's worth noting that a $(TUnitVersion) MSBuild property set at the repo level could simplify future bumps. Not a concern for this PR.

✅ Safe to merge.