chore(deps): update tunit to 1.18.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	1.17.54 → 1.18.0
TUnit.AspNetCore	nuget	minor	1.17.54 → 1.18.0
TUnit.Assertions	nuget	minor	1.17.54 → 1.18.0
TUnit.Assertions.FSharp	nuget	minor	1.17.54 → 1.18.0
TUnit.Core	nuget	minor	1.17.54 → 1.18.0
TUnit.Engine	nuget	minor	1.17.54 → 1.18.0
TUnit.Playwright	nuget	minor	1.17.54 → 1.18.0

---

Release Notes

thomhurst/TUnit (TUnit)

v1.18.0: 1.18.0

What's Changed

Other Changes

• refactor: convert 15 manual assertions to [GenerateAssertion] by @​thomhurst in #​5029
• Fix invisible chart labels on benchmark pages by @​Copilot in #​5033
• docs: fix position of --results-directory in documentation by @​vbreuss in #​5038
• fix: IsEquivalentTo falls back to Equals() for types with no public members by @​thomhurst in #​5041
• perf: make test metadata creation fully synchronous by @​thomhurst in #​5045
• perf: eliminate <>c display class from generated TestSource classes by @​thomhurst in #​5047
• perf: generate per-class helper to reduce JIT compilations by ~18,000 by @​thomhurst in #​5048
• perf: consolidate per-method TestSource into per-class TestSource (~27k fewer JITs) by @​thomhurst in #​5049
• perf: eliminate per-class TestSource .ctor JITs via delegate registration by @​thomhurst in #​5051
• feat: rich HTML test reports by @​thomhurst in #​5044

Dependencies

• chore(deps): update tunit to 1.17.54 by @​thomhurst in #​5028
• chore(deps): update dependency polyfill to 9.13.0 by @​thomhurst in #​5035
• chore(deps): update dependency polyfill to 9.13.0 by @​thomhurst in #​5036

Full Changelog: v1.17.54...v1.18.0

---

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: chore(deps): update tunit to 1.18.0

This is a straightforward Renovate bot dependency update bumping all TUnit packages from 1.17.54 to 1.18.0. The changes are minimal and mechanical.

What Changed

All TUnit package references are uniformly updated across two locations:

• Directory.Packages.props — central version management for 6 packages (TUnit, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Assertions, TUnit.Assertions.FSharp)
• TUnit.Templates/content/ — template project files for 5 templates, hardcoding explicit versions as expected for end-user templates

Assessment

The changes are correct and complete. All affected packages are updated consistently to the same target version (1.18.0), and no package appears to have been missed.

Notable release highlights in 1.18.0 (visible in the PR description):

• Several significant perf wins: ~18k fewer JIT compilations from per-class helper generation, ~27k fewer JITs from TestSource consolidation, and metadata creation made fully synchronous
• Bug fix for IsEquivalentTo falling back to Equals() for types with no public members
• Rich HTML test reports feature

Template versioning design: The template files intentionally use hardcoded versions (separate from central package management), which is the correct approach — templates are shipped as-is to end users who need a concrete, pinned version to start from. The dual-update pattern is expected here.

No issues found. This is a clean, routine dependency bump that should be safe to merge with auto-merge enabled.

[claude]

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

This is a straightforward Renovate Bot dependency update bumping all TUnit-family packages from 1.17.54 → 1.18.0. Here's my analysis:

What's Changed

7 packages updated consistently across two locations:

• Directory.Packages.props — central package version management for internal test/example projects
• TUnit.Templates/content/ — project scaffold templates shipped to end-users

Assessment

No issues found. The update is clean and consistent:

• All 7 packages (TUnit, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Core, TUnit.Engine, TUnit.AspNetCore, TUnit.Playwright) are bumped in lockstep — no version drift between related packages.
• Template files correctly pin to an explicit released version (rather than floating * or 1.18.*), which is the right approach for project scaffolds. Users get a reproducible, known-good starting point.
• The 1.18.0 release includes meaningful improvements this repo ships: significant JIT reduction (~45k fewer per the release notes), the IsEquivalentTo bug fix, and the new rich HTML test reports feature — all good reasons to have templates point at this version.

Minor Observation

The template files in TUnit.Templates/content/ carry pinned versions independently of Directory.Packages.props. If these ever drift (e.g., a future Renovate run misses one), users could scaffold projects with mixed versions. This is an existing structural pattern, not introduced by this PR, but worth noting for the long term. A single source-of-truth for template versions (e.g., MSBuild property injection at template pack time) would eliminate that risk entirely — but that's a separate refactoring concern.

Approved as-is.

[claude]

Clean, consistent dependency bump. Approved.