chore(deps): update tunit to 1.19.74

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.19.57 → 1.19.74
TUnit.AspNetCore	nuget	patch	1.19.57 → 1.19.74
TUnit.Assertions	nuget	patch	1.19.57 → 1.19.74
TUnit.Assertions.FSharp	nuget	patch	1.19.57 → 1.19.74
TUnit.Core	nuget	patch	1.19.57 → 1.19.74
TUnit.Engine	nuget	patch	1.19.57 → 1.19.74
TUnit.Playwright	nuget	patch	1.19.57 → 1.19.74

---

Release Notes

thomhurst/TUnit (TUnit)

v1.19.74: 1.19.74

What's Changed

Other Changes

• feat: per-hook activity spans with method names by @​thomhurst in #​5159
• fix: add tooltip to truncated span names in HTML report by @​thomhurst in #​5164
• Use enum names instead of numeric values in test display names by @​Copilot in #​5178
• fix: resolve CS8920 when mocking interfaces whose members return static-abstract interfaces by @​lucaxchaves in #​5154

Dependencies

• chore(deps): update tunit to 1.19.57 by @​thomhurst in #​5157
• chore(deps): update dependency gitversion.msbuild to 6.6.1 by @​thomhurst in #​5160
• chore(deps): update dependency gitversion.tool to v6.6.1 by @​thomhurst in #​5161
• chore(deps): update dependency polyfill to 9.20.0 by @​thomhurst in #​5163
• chore(deps): update dependency polyfill to 9.20.0 by @​thomhurst in #​5162
• chore(deps): update dependency polyfill to 9.21.0 by @​thomhurst in #​5166
• chore(deps): update dependency polyfill to 9.21.0 by @​thomhurst in #​5167
• chore(deps): update dependency polyfill to 9.22.0 by @​thomhurst in #​5168
• chore(deps): update dependency polyfill to 9.22.0 by @​thomhurst in #​5169
• chore(deps): update dependency coverlet.collector to 8.0.1 by @​thomhurst in #​5177

New Contributors

• @​lucaxchaves made their first contribution in #​5154

Full Changelog: v1.19.57...v1.19.74

---

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]

This is a Renovate bot-generated patch bump of TUnit packages from 1.19.57 to 1.19.74. The diff is mechanical and correct — all seven package references are updated consistently.

A few observations worth keeping in mind as the project evolves:

Template projects pin versions explicitly instead of inheriting from Directory.Packages.props

The files under TUnit.Templates/content/ (TestProject.csproj, TestProject.fsproj, TestProject.vbproj, etc.) carry hard-coded Version="..." attributes on their <PackageReference> elements. This means every patch bump like this one must touch both Directory.Packages.props AND every template project file individually. At 7 packages × 6 template files the surface area will only grow.

If the template projects could reference versions via a common mechanism (e.g., a shared .props file bundled with the template, or a global.json-equivalent for NuGet like a Directory.Packages.props inside the template content root), automated bumps would only need to update a single file and the template projects would stay correct automatically. This also reduces the risk of a future PR where one template file is missed.

No architectural or logic concerns — this is purely a version bump with no behavioural changes in the codebase itself. Auto-merge via squash looks appropriate here.

[claude]

Review: Dependency Update — TUnit packages 1.19.57 → 1.19.74

This is a Renovate-generated patch-level bump across all TUnit packages. The change is mechanically correct and safe to merge. A few observations worth noting:

Version consistency

All seven TUnit packages (TUnit, TUnit.AspNetCore, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Core, TUnit.Engine, TUnit.Playwright) are bumped uniformly to 1.19.74. This is correct — partial version mismatches between these packages can cause subtle runtime issues, especially since TUnit.Core and TUnit.Engine must agree on metadata contracts in both source-gen and reflection modes.

Template project versioning vs. central package management

The template projects under TUnit.Templates/content/ pin versions directly in their .csproj/.fsproj files rather than using Directory.Packages.props. This is intentional since these are scaffolding outputs that users copy out to a fresh location, but it does create a maintenance burden: every patch bump requires touching both Directory.Packages.props and each template file individually. If the template projects were structured to reference a <TUnitVersion> MSBuild property sourced from a shared props file during template generation, this dual-maintenance pattern could be eliminated. That said, this is a pre-existing design choice and out of scope for this PR.

What ships in 1.19.74

Based on the release notes included in the PR description, the notable changes bundled in this range include:

• Per-hook activity spans with method names (#5159)
• Tooltip fix for truncated span names in HTML report (#5164)
• Enum names instead of numeric values in test display names (#5178) — this is a user-visible behavioural change worth being aware of if any snapshot tests compare display names containing enum arguments
• CS8920 fix for static-abstract interface mocking (#5154)

The enum display name change (#5178) in particular could affect snapshot-tested output. If any .verified.txt files in TUnit.Core.SourceGenerator.Tests include test display names that previously showed enum integer values, those snapshots will need to be re-accepted after this bump. It is worth verifying the snapshot tests pass as part of merging this.

Overall

The change itself is correct and minimal. Auto-merge with the standard CI gate is appropriate here.