chore(deps): update tunit to 1.32.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	1.31.0 → 1.32.0
TUnit.AspNetCore	nuget	minor	1.31.0 → 1.32.0
TUnit.Assertions	nuget	minor	1.31.0 → 1.32.0
TUnit.Assertions.FSharp	nuget	minor	1.31.0 → 1.32.0
TUnit.Core	nuget	minor	1.31.0 → 1.32.0
TUnit.Engine	nuget	minor	1.31.0 → 1.32.0
TUnit.Playwright	nuget	minor	1.31.0 → 1.32.0

---

Release Notes

thomhurst/TUnit (TUnit)

v1.32.0: 1.32.0

What's Changed

Other Changes

• fix: auto-register correlated logging for minimal API hosts (#​5503) by @​thomhurst in #​5511
• fix: cascade HookExecutorAttribute from class/assembly to hooks (#​5462) by @​thomhurst in #​5512

Dependencies

• chore(deps): update dependency polyfill to 10.3.0 by @​thomhurst in #​5508
• chore(deps): update tunit to 1.31.0 by @​thomhurst in #​5510
• chore(deps): update dependency polyfill to 10.3.0 by @​thomhurst in #​5509

Full Changelog: v1.31.0...v1.32.0

---

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

This is a clean, straightforward Renovate-generated dependency bump from TUnit 1.31.0 → 1.32.0 across all 7 TUnit-family packages.

Summary

Files changed:

• Directory.Packages.props — central package version management, all TUnit packages bumped consistently
• 5 template project files (, , ) in TUnit.Templates/ — hardcoded versions bumped in lockstep

Assessment: ✅ Looks good

Consistency — All 7 packages are bumped to the same version (1.32.0) with no partial upgrades. No version skew introduced.

Release content — The 1.32.0 release brings two bug fixes directly relevant to this codebase:

• fix: auto-register correlated logging for minimal API hosts (#5511) — improves AspNetCore integration
• fix: cascade HookExecutorAttribute from class/assembly to hooks (#5512) — fixes attribute inheritance behaviour

Both are regression fixes that make sense to pick up promptly.

Template versioning — Template project files intentionally carry hardcoded package versions rather than deferring to Directory.Packages.props. This is the correct approach: when a user scaffolds a new project from these templates the parent Directory.Packages.props won't be present, so self-contained pinned versions are required. The trade-off (versions must be updated in both places) is exactly what this PR handles correctly.

No concerns. Safe to merge.

[claude]

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

This is a clean, straightforward Renovate-generated dependency bump from TUnit 1.31.0 -> 1.32.0 across all 7 TUnit-family packages.

Summary

Files changed:

• Directory.Packages.props — central package version management, all TUnit packages bumped consistently
• 5 template project files in TUnit.Templates/ — hardcoded versions bumped in lockstep

Assessment: Looks good

Consistency — All 7 packages are bumped to the same version (1.32.0) with no partial upgrades. No version skew introduced.

Release content — The 1.32.0 release brings two bug fixes directly relevant to this codebase:

• fix: auto-register correlated logging for minimal API hosts (#5511) — improves AspNetCore integration
• fix: cascade HookExecutorAttribute from class/assembly to hooks (#5512) — fixes attribute inheritance behaviour

Both are regression fixes that make sense to pick up promptly.

Template versioning — Template project files intentionally carry hardcoded package versions rather than deferring to Directory.Packages.props. This is the correct approach: when a user scaffolds a new project from these templates, the parent Directory.Packages.props won't be present, so self-contained pinned versions are required. The trade-off (versions must be updated in both places) is exactly what this PR handles correctly.

No concerns. Safe to merge.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

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