Update TUnit to 1.64.13

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
TUnit	1.64.6 → 1.64.13
TUnit.Assertions	1.64.6 → 1.64.13
TUnit.Core	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 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: 14 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: 61e20945-acaa-4e82-9e1c-044b79fedc03

📥 Commits

Reviewing files that changed from the base of the PR and between 991605c and 1936d27.

📒 Files selected for processing (1)

• Directory.Packages.props

---

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

[claude]

Code review

No issues found. This is an automated Renovate dependency bump limited to Directory.Packages.props, updating TUnit, TUnit.Assertions, and TUnit.Core from 1.64.6 to 1.64.13 (patch release). The change is a straightforward version bump with no code/architecture impact to review — safe to merge pending CI.