chore(deps): update tunit to 1.64.6

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.64.0 → 1.64.6
TUnit.AspNetCore	nuget	patch	1.64.0 → 1.64.6
TUnit.Assertions	nuget	patch	1.64.0 → 1.64.6
TUnit.Assertions.FSharp	nuget	patch	1.64.0 → 1.64.6
TUnit.Core	nuget	patch	1.64.0 → 1.64.6
TUnit.Engine	nuget	patch	1.64.0 → 1.64.6

---

Release Notes

thomhurst/TUnit (TUnit)

v1.64.6: 1.64.6

What's Changed

Other Changes

• Switch NuGet publishing to trusted publishing by @​thomhurst in #​6573
• Expose results directory through TestContext by @​thomhurst in #​6575
• Fix outcome timeline overflow in HTML reports by @​thomhurst in #​6574

Dependencies

• chore(deps): update tunit to 1.64.0 by @​thomhurst in #​6570

Full Changelog: v1.64.0...v1.64.6

---

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 Mend Renovate CLI.

[coderabbitai]

Warning

Review limit reached

@thomhurst, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7bf21aac-93c4-4d69-a2df-75dfc8b1c257

📥 Commits

Reviewing files that changed from the base of the PR and between a3da74c and 9151926.

📒 Files selected for processing (1)

• Directory.Packages.props

---

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

Updates the centrally managed TUnit package family from 1.64.0 to 1.64.6.

• Keeps TUnit, TUnit.Core, TUnit.Engine, TUnit.Assertions, TUnit.Assertions.FSharp, and TUnit.AspNetCore aligned on the same patch version.

Confidence Score: 5/5

The PR appears safe to merge because the coordinated patch update preserves package-family version alignment and no actionable defect was identified.

The only changed behavior is central dependency resolution to TUnit 1.64.6, with every related TUnit package updated consistently.

Important Files Changed

Filename	Overview
Directory.Packages.props	Updates six related TUnit package versions together without introducing a version-alignment issue.

_{Reviews (1): Last reviewed commit: "chore(deps): update tunit to 1.64.6" | Re-trigger Greptile}

[claude]

Code Review

This is a trivial, automated Renovate dependency-version bump — Directory.Packages.props updates TUnit's self-referencing NuGet packages (TUnit, TUnit.AspNetCore, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Core, TUnit.Engine) from 1.64.0 → 1.64.6, a patch release.

Findings: none.

• No logic changes, no removed behavior, no new code paths, no call sites affected.
• No CLAUDE.md rule violations (no source-gen/reflection dual-mode changes, no snapshot-affecting output, no VSTest usage, no AOT/perf-sensitive code touched).
• Target version 1.64.6 corresponds to a real upstream release containing only unrelated bug fixes/chores (trusted publishing, TestContext results directory, HTML report overflow fix) — nothing that interacts with this repo's own code.

LGTM — safe to merge (or let automerge handle it) as-is.