chore(deps): update tunit to 1.65.31

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.65.0 → 1.65.31
TUnit.AspNetCore	nuget	patch	1.65.0 → 1.65.31
TUnit.Assertions	nuget	patch	1.65.0 → 1.65.31
TUnit.Assertions.FSharp	nuget	patch	1.65.0 → 1.65.31
TUnit.Core	nuget	patch	1.65.0 → 1.65.31
TUnit.Engine	nuget	patch	1.65.0 → 1.65.31

---

Release Notes

thomhurst/TUnit (TUnit)

v1.65.31: 1.65.31

What's Changed

Other Changes

• Add xunit.v3.aot to speed comparison by @​campersau in #​6621
• Suppress HTML reports for nested test runs by @​thomhurst in #​6620
• Address xUnit speed comparison review feedback by @​thomhurst in #​6623
• Fix docs TypeScript 7 compatibility by @​thomhurst in #​6625
• Refresh docs npm dependencies by @​thomhurst in #​6624
• Switch to SignalWire llms.txt plugin by @​thomhurst in #​6627
• Remove single-test discovery copies by @​thomhurst in #​6631
• Skip unused scheduler work for unconstrained suites by @​thomhurst in #​6632
• Skip empty test registration work by @​thomhurst in #​6628
• Skip absent hook pipelines by @​thomhurst in #​6630
• Fix mocks with inaccessible constructor parameter types by @​thomhurst in #​6635

Dependencies

• chore(deps): update dependency awssdk.sqs to 4.0.100.8 by @​thomhurst in #​6608
• chore(deps): update tunit to 1.65.0 by @​thomhurst in #​6609
• chore(deps): update dependency testcontainers.postgresql to 4.14.0 by @​thomhurst in #​6612
• chore(deps): update dependency testcontainers.kafka to 4.14.0 by @​thomhurst in #​6611
• chore(deps): update dependency testcontainers.redis to 4.14.0 by @​thomhurst in #​6613
• chore(deps): update dependency microsoft.net.test.sdk to 18.9.0 by @​thomhurst in #​6614
• chore(deps): update xunit to v4 by @​thomhurst in #​6616

Full Changelog: v1.65.0...v1.65.31

---

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.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[greptile-apps]

Greptile Summary

Updates the centrally managed TUnit package family from 1.65.0 to 1.65.31.

• Keeps TUnit, Core, Engine, Assertions, FSharp assertions, and ASP.NET Core integration on the same patch version.
• Does not change application or test logic.

Confidence Score: 5/5

The PR appears safe to merge because the related TUnit packages remain version-aligned and no concrete restore, build, or runtime failure was identified.

The change is limited to a coordinated patch-version update of centrally managed packages, with no established incompatible API use, conflicting constraint, or omitted lock-file update.

Important Files Changed

Filename	Overview
Directory.Packages.props	Consistently updates all six centrally managed TUnit package entries to 1.65.31; no concrete compatibility or version-alignment defect was identified.

_{Reviews (1): Last reviewed commit: "chore(deps): update tunit to 1.65.31" | 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: 58 minutes

Limit details: You’ve used all 3 included reviews currently available.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 34d958dd-89bc-4523-9182-f6cd1d42a9e9

📥 Commits

Reviewing files that changed from the base of the PR and between 9760b07 and 533e768.

📒 Files selected for processing (1)

• Directory.Packages.props

---

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