chore(deps): update tunit to 1.17.4

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.17.0 → 1.17.4
TUnit.AspNetCore	nuget	patch	1.17.0 → 1.17.4
TUnit.Assertions	nuget	patch	1.17.0 → 1.17.4
TUnit.Assertions.FSharp	nuget	patch	1.17.0 → 1.17.4
TUnit.Core	nuget	patch	1.17.0 → 1.17.4
TUnit.Engine	nuget	patch	1.17.0 → 1.17.4
TUnit.Playwright	nuget	patch	1.17.0 → 1.17.4

---

Release Notes

thomhurst/TUnit (TUnit)

v1.17.4: 1.17.4

What's Changed

Other Changes

• feat: strongly-typed event raises and event subscription API by @​thomhurst in #​4978

Dependencies

• chore(deps): update tunit to 1.17.0 by @​thomhurst in #​4975
• chore(deps): update dependency polyfill to 9.10.0 by @​thomhurst in #​4977
• chore(deps): update dependency polyfill to 9.10.0 by @​thomhurst in #​4976

Full Changelog: v1.17.0...v1.17.4

---

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]

Code Review

This is a straightforward Renovate-generated patch update bumping TUnit packages from 1.17.0 to 1.17.4. The changes are mechanical and consistent across both the central Directory.Packages.props and the template project files.

Observation: Version Inconsistency with TUnit.AspNetCore

TUnit.AspNetCore in Directory.Packages.props remains at 1.17.0 while all other TUnit packages were bumped to 1.17.4. Renovate did not include it in this PR's update list, which suggests it may be versioned independently or was already excluded from the Renovate config scope. Worth verifying that TUnit.AspNetCore 1.17.0 is compatible with the newly referenced 1.17.4 engine/core packages — mismatched versions between closely coupled packages in the same ecosystem can occasionally cause subtle build or runtime issues.

If TUnit.AspNetCore is released on the same cadence and 1.17.4 exists, consider aligning it manually or ensuring it's covered by the Renovate configuration.

Everything Else Looks Good

• All six listed packages are updated consistently.
• Both Directory.Packages.props (centralized NuGet versioning) and the individual template .csproj/.fsproj/.vbproj files are kept in sync.
• The patch bump is low-risk and the changelog confirms no breaking changes.

[claude]

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

This is a Renovate Bot automated patch update (1.17.0 → 1.17.4) across all TUnit self-referencing package dependencies. The changes are straightforward and correct.

What's being updated

• Directory.Packages.props — Central Package Management versions for TUnit, TUnit.Assertions, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Assertions.FSharp
• TUnit.Templates/content/* — Hardcoded version strings in all six template project files (C#, F#, VB, AspNet, Playwright variants)

Observations

Template version pinning is intentional. The template project files carry explicit versions rather than relying on Directory.Packages.props, which is correct — templates are distributed standalone and need pinned versions so consumers get a reproducible starting point regardless of what CPM versions exist in the repo at any given time.

Consistency is maintained. All seven package references are bumped in lock-step to 1.17.4, with no packages left behind at 1.17.0. The TUnit.Playwright package is correctly updated only in its template file (it has no entry in Directory.Packages.props), which matches the existing structure.

Release notes are clear. v1.17.4 brings the strongly-typed event raises/subscription API from #4978, plus dependency housekeeping. No breaking changes in this patch range.

No issues found

The update is mechanical, complete, and internally consistent. Automerge should be safe to proceed.

[claude]

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

This is the third look at this Renovate-generated patch bump (1.17.0 → 1.17.4).

Addressing Previous Review Concerns

The first review flagged a potential inconsistency where TUnit.AspNetCore might have been left behind at 1.17.0. Looking at the actual diff, that concern was unfounded — TUnit.AspNetCoreis updated to 1.17.4 in Directory.Packages.props alongside all other TUnit packages. All seven packages are updated consistently.

Change Summary

Location	Packages Updated
Directory.Packages.props	TUnit, TUnit.Assertions, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Assertions.FSharp
Template .csproj/.fsproj/.vbproj files (6 files)	TUnit, TUnit.Assertions.FSharp, TUnit.Playwright

Assessment

• Complete: All TUnit references across both central CPM and template project files are aligned at 1.17.4.
• Consistent: No package left at a stale version.
• Low-risk: Patch bump with changelog confirming no breaking changes (v1.17.4 adds the strongly-typed event raises/subscription API from #4978).
• Template pinning: Hardcoded versions in template files remain correct — templates must carry explicit versions for reproducibility when distributed standalone.

No issues found. Safe to automerge.