[thomhurst]

This PR contains the following updates:

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

---

Release Notes

thomhurst/TUnit (TUnit)

v1.31.0: 1.31.0

What's Changed

Other Changes

• feat(reporters): overhaul GitHub Actions step summary by @​thomhurst in #​5483
• fix: truncate large stdout/stderr in HTML report to prevent JSON serialization failure by @​thomhurst in #​5485
• feat(html-report): add failure clustering to test report by @​thomhurst in #​5490
• feat(html-report): add chevron affordance to failure cluster headers by @​thomhurst in #​5492
• feat(reporters): group GitHub summary failures by exception type by @​thomhurst in #​5491
• feat(reporters): add minimap sidebar navigator to HTML report by @​thomhurst in #​5494
• feat(html-report): add category/tag filter pills to toolbar by @​thomhurst in #​5496
• feat(html-report): omit redundant test body span from trace timeline by @​thomhurst in #​5497
• fix(tests): clear reporter env vars before each GitHubReporterTest to fix flaky CI on macOS/Windows by @​thomhurst in #​5499
• feat: add TestContext.MakeCurrent() for console output correlation by @​thomhurst in #​5502
• feat(html-report): add flaky test detection and summary section by @​thomhurst in #​5498
• fix: smarter stack trace filtering that preserves TUnit-internal traces by @​thomhurst in #​5506
• feat: add Activity baggage-based test context correlation by @​thomhurst in #​5505

Dependencies

• chore(deps): update actions/github-script action to v9 by @​thomhurst in #​5476
• chore(deps): update tunit to 1.30.8 by @​thomhurst in #​5477
• chore(deps): update dependency polyfill to 10.2.0 by @​thomhurst in #​5482
• chore(deps): update dependency polyfill to 10.2.0 by @​thomhurst in #​5481
• chore(deps): update actions/upload-artifact action to v7.0.1 by @​thomhurst in #​5495

Full Changelog: v1.30.8...v1.31.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.31.0

This is a Renovate Bot–generated dependency bump (seven TUnit packages 1.30.8 → 1.31.0) across Directory.Packages.props and five template project files. The version bump itself is correct and complete. A few structural observations worth noting:

---

Finding 1 — Inconsistent Template Versioning Strategy (Medium)

The template project files use two different versioning strategies, and this PR perpetuates the inconsistency:

• TUnit.Templates/content/TUnit/TestProject.csproj — uses a floating minor range: Version="1.*"
• All other templates (AspNet, FSharp, AspNet.FSharp, VB, Playwright) — use pinned exact versions: Version="1.31.0"

Why this matters: Two weeks after this PR merges, users who instantiate any of the five pinned templates will get a version that's already stale, while users of the main C# template always get the latest 1.x. This creates an uneven user experience that worsens over time.

Suggested fix: Standardise all templates on Version="1.*" (or all pinned, if reproducibility is preferred). Doing so would also mean Renovate PRs like this one wouldn't need to touch template files at all.

---

Finding 2 — TUnit.Aspire Templates Not Tracked by Renovate (Low)

The two Aspire templates still reference TUnit.Aspire Version="1.14.0" while the other packages are at 1.31.0. If TUnit.Aspire follows the same version cadence, these templates are significantly behind.

Root cause: TUnit.Aspire is not listed in Directory.Packages.props, so Renovate doesn't track it. Adding it to CPM would bring it under automated updates alongside the other packages.

---

Finding 3 — Test Harness Blind Spot (Informational)

TemplateTestBase.ScrubVersions scrubs all Version="…" values to 0.0.0-scrubbed before snapshot comparison. This is correct for avoiding false-positive snapshot failures on version bumps, but it also means the inconsistency in Finding 1 (floating 1.* vs. pinned 1.31.0) is invisible to the test suite. Something to keep in mind if the versioning strategy is ever revisited.

---

Verdict

Safe to merge as-is — the bump is correct for the packages Renovate tracks. Findings 1 and 2 are pre-existing structural issues best addressed in a follow-up PR:

1. Standardise all template Version values to 1.*
2. Add TUnit.Aspire to Directory.Packages.props so Renovate tracks it automatically

[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}