chore(deps): update tunit to 1.37.10

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
TUnit	1.37.0 → 1.37.10
TUnit.Assertions	1.37.0 → 1.37.10
TUnit.Core	1.37.0 → 1.37.10

---

Release Notes

thomhurst/TUnit (TUnit)

v1.37.10: 1.37.10

What's Changed

Other Changes

• docs(test-filters): add migration callout for --filter → --treenode-filter by @​johnkattenhorn in #​5628
• fix: re-enable RPC tests and modernize harness (#​5540) by @​thomhurst in #​5632
• fix(mocks): propagate [Obsolete] and null-forgiving raise dispatch (#​5626) by @​JohnVerheij in #​5631
• ci: use setup-dotnet built-in NuGet cache by @​thomhurst in #​5635
• feat(playwright): propagate W3C trace context into browser contexts by @​thomhurst in #​5636

Dependencies

• chore(deps): update tunit to 1.37.0 by @​thomhurst in #​5625

New Contributors

• @​johnkattenhorn made their first contribution in #​5628
• @​JohnVerheij made their first contribution in #​5631

Full Changelog: thomhurst/TUnit@v1.37.0...v1.37.10

---

Configuration

📅 Schedule: (UTC)

• 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.37.10

Summary

This is a routine Renovate Bot patch dependency update bumping three TUnit packages from 1.37.0 → 1.37.10 in Directory.Packages.props:

• TUnit
• TUnit.Assertions
• TUnit.Core

✅ Positive Aspects

1. Atomic update — All three interdependent TUnit packages are bumped together in one PR, preventing version skew that would cause compilation or runtime failures.
2. Centralized Package Management — Using Directory.Packages.props (CPM) means this 3-line change propagates consistently to all 6 consuming test projects. Excellent architectural practice.
3. Minimal diff — 3 lines changed, 1 file. Exactly as much as needed.
4. No breaking changes — The 1.37.0 → 1.37.10 range contains only fixes (obsolete attribute propagation in mocks, RPC test fixes), CI improvements (dotnet setup cache), and a Playwright W3C trace context feature — none of which are breaking.

💡 Suggestion (not a blocker)

The three TUnit.* packages are co-released and must always be version-locked together. This currently works by coincidence of shared versioning. Adding an explicit Renovate grouping rule in renovate.json would make that intent explicit and more resilient:

"packageRules": [
  { "matchPackagePrefixes": ["TUnit"], "groupName": "TUnit packages" }
]

Why this is better: If TUnit ever releases packages on slightly different cadences (e.g., a hotfix to TUnit.Assertions only), Renovate would currently open separate PRs for each — which would temporarily break the version lock. An explicit group rule prevents that scenario entirely.

Verdict

Safe to merge once CI passes. No correctness concerns.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	✅ 0 (≤ 20 complexity)

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}