chore(deps): update tunit to 1.19.22

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
TUnit	1.19.16 → 1.19.22
TUnit.Assertions	1.19.16 → 1.19.22
TUnit.Core	1.19.16 → 1.19.22

---

Release Notes

thomhurst/TUnit (TUnit)

v1.19.22: 1.19.22

What's Changed

Other Changes

• Remove redundant prefixes from tracing timeline spans by @​thomhurst in #​5111
• Render span tags and events on separate lines by @​thomhurst in #​5113
• Demote granular internal logs from Debug to Trace level by @​thomhurst in #​5116

Dependencies

• chore(deps): update tunit to 1.19.16 by @​thomhurst in #​5109

Full Changelog: thomhurst/TUnit@v1.19.16...v1.19.22

---

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

This is a straightforward dependency update PR generated by Renovate Bot, bumping three TUnit packages from 1.19.16 to 1.19.22.

Changes

• TUnit: 1.19.16 → 1.19.22
• TUnit.Assertions: 1.19.16 → 1.19.22
• TUnit.Core: 1.19.16 → 1.19.22

All three packages are updated consistently in Directory.Packages.props using centralized package version management — the correct approach for a multi-project solution.

Assessment

No issues found. This is a patch-level version bump (1.19.16 → 1.19.22) with only minor, non-breaking changes:

• Removal of redundant prefixes from tracing timeline spans
• Rendering span tags and events on separate lines
• Demoting granular internal logs from Debug to Trace level

These are all internal improvements to TUnit's diagnostics/tracing output with no API surface changes, so there is no risk of breaking existing tests.

The use of centralized package management via Directory.Packages.props ensures all three TUnit packages are kept in lockstep, which is the right pattern — version mismatches between TUnit, TUnit.Assertions, and TUnit.Core could otherwise cause subtle compatibility issues.

Approved — safe to merge.

[claude]

Code Review: chore(deps): update TUnit to 1.19.22

This is a routine Renovate Bot dependency update bumping all three TUnit packages from 1.19.16 to 1.19.22 in Directory.Packages.props.

Previous Review

A prior review was already submitted for this PR — no issues were raised at that time.

Current Assessment

No issues found. The change remains a straightforward, low-risk patch-level version bump:

• All three packages (TUnit, TUnit.Assertions, TUnit.Core) are updated consistently and in lockstep — correct practice to avoid version mismatch issues.
• Uses centralized package management via Directory.Packages.props — the right pattern for a multi-project solution.
• Release notes confirm the changes are internal diagnostics/tracing improvements with no API surface changes, so no risk to existing tests.

Approved — safe to merge.