chore(deps): update dependency tunit to 1.64.13

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.64.6 → 1.64.13

---

Release Notes

thomhurst/TUnit (TUnit)

v1.64.13: 1.64.13

What's Changed

Other Changes

• Stabilize immediate WaitsFor assertion test by @​thomhurst in #​6576
• fix: Allow Item.Member after HasSingleItem by @​SnakyBeaky in #​6583

Dependencies

• chore(deps): update tunit to 1.64.6 by @​thomhurst in #​6577
• chore(deps): update dependency nsubstitute to 6.2.0 by @​thomhurst in #​6580
• chore(deps): update dependency microsoft.playwright to 1.62.0 by @​thomhurst in #​6582
• chore(deps): update dependency microsoft.net.stringtools to 18.9.6 by @​thomhurst in #​6584

New Contributors

• @​SnakyBeaky made their first contribution in #​6583

Full Changelog: thomhurst/TUnit@v1.64.6...v1.64.13

---

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 this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[greptile-apps]

Greptile Summary

Updates the unit-test framework dependency from TUnit 1.64.6 to 1.64.13.

• Applies the patch-version upgrade to the unit-test project.
• Leaves application code and test implementation unchanged.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

The change is limited to a patch-level test dependency update, and the repository’s existing target frameworks, test APIs, package configuration, and test infrastructure reveal no concrete incompatible behavior.

Important Files Changed

Filename	Overview
EnumerableAsyncProcessor.UnitTests/EnumerableAsyncProcessor.UnitTests.csproj	Updates the TUnit package reference by seven patch releases; no concrete compatibility or configuration issue was identified.

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 21 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: a23b3d88-6eb2-4d53-a70d-aa62ad2dfb8c

📥 Commits

Reviewing files that changed from the base of the PR and between e9cc67f and fab3ce4.

📒 Files selected for processing (1)

• EnumerableAsyncProcessor.UnitTests/EnumerableAsyncProcessor.UnitTests.csproj

---

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