chore(deps): update tunit to 1.46.0 by thomhurst · Pull Request #6065 · thomhurst/TUnit (original) (raw)

PR Review: chore(deps): update tunit to 1.46.0

Summary

Automated Renovate bot PR bumping 6 TUnit-family NuGet package references in Directory.Packages.props from 1.45.29 → 1.46.0. Purely mechanical version string replacements — no logic, configuration, or test code changed.

Self-Dependency Pattern (Informational)

This repo dogfoods its own published packages via Renovate, which is the established pattern here. One thing worth keeping in mind: once this merges, any further local source changes that haven't been published yet will create a gap between what the integration tests reference (the published 1.46.0 NuGet) and the current source-under-development. This is a known trade-off of the dogfooding setup, not a defect.

What 1.46.0 Includes (Per PR Body)

• Treenode-filter parenthesised-segment fix (#6027)
• Per-session state isolation under MTP server-mode concurrency (#6025)
• Source span population in generated test metadata (#5991)
• Upstream dependency bumps

No breaking changes; no corresponding updates required in consuming test projects.

Issues

None. The diff is exactly what it should be.

Strengths

• Atomic versioning: All 6 TUnit packages move together to the same version — no risk of TUnit.Core/TUnit.Engine skew causing runtime mismatches.
• Central Package Management: Single-file update via Directory.Packages.props is the correct architecture for a multi-project repo.
• Automerge-appropriate: Routine self-package bump with CI as the only meaningful gate.

Verdict

✅ Approve — merge when CI is green. Clean, correct, minimal automated update.