chore(deps): update tunit to 1.43.11

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	1.43.2 → 1.43.11
TUnit.AspNetCore	nuget	patch	1.43.2 → 1.43.11
TUnit.Assertions	nuget	patch	1.43.2 → 1.43.11
TUnit.Assertions.FSharp	nuget	patch	1.43.2 → 1.43.11
TUnit.Core	nuget	patch	1.43.2 → 1.43.11
TUnit.Engine	nuget	patch	1.43.2 → 1.43.11

---

Release Notes

thomhurst/TUnit (TUnit)

v1.43.11: 1.43.11

What's Changed

Other Changes

• perf(engine): skip execution ledger for independent tests by @​thomhurst in #​5813
• perf(engine): skip tracked object graph rediscovery by @​thomhurst in #​5814
• fix: suppress XML doc warnings in generated sources by @​mvanhorn in #​5797
• Fix xUnit Throws migration docs by @​thomhurst in #​5819
• Fix Should optional overload generation by @​thomhurst in #​5820

Dependencies

• chore(deps): update dependency mockolate to 3.1.0 by @​thomhurst in #​5811
• chore(deps): update tunit to 1.43.2 by @​thomhurst in #​5809
• chore(deps): update dependency nunit.analyzers to 4.13.0 by @​thomhurst in #​5815
• chore(deps): update dependency yaml to v2.8.4 by @​thomhurst in #​5812

New Contributors

• @​mvanhorn made their first contribution in #​5797

Full Changelog: v1.43.2...v1.43.11

---

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.

[claude]

Code Review

This is a clean Renovate-generated patch bump of all TUnit NuGet packages from 1.43.2 → 1.43.11 in Directory.Packages.props.

What's good

• Version consistency — all six TUnit-family packages are bumped together to the same version (1.43.11), which is the right approach. Mixing versions of TUnit, TUnit.Core, TUnit.Engine, etc. would risk subtle compatibility issues.
• Minimal scope — the diff is exactly what it should be: only version strings in the central package management file.
• Valuable content in the 9 patch releases — the included changes (two engine performance improvements, generated-source XML doc warning suppression fix, assertion overload generation fix) are all low-risk improvements worth pulling in.

One observation worth noting

This repo is updating its own published packages (dogfooding pattern — TUnit tests itself using TUnit). The versions in Directory.Packages.props represent the published NuGet releases used by integration/example test projects, not the source being built in this repo. That's the correct model, but it means the CI pipeline is the only real validation that the published 1.43.11 works correctly against whatever source is currently on main. Since auto-merge is enabled, the CI result is the authoritative gate here.

Verdict

No issues. The change is correct, complete, and appropriately scoped. Good to merge once CI is green.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}