chore(deps): update tunit to 1.43.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	1.41.0 → 1.43.2
TUnit.AspNetCore	nuget	minor	1.41.0 → 1.43.2
TUnit.Assertions	nuget	minor	1.41.0 → 1.43.2
TUnit.Assertions.FSharp	nuget	minor	1.41.0 → 1.43.2
TUnit.Core	nuget	minor	1.41.0 → 1.43.2
TUnit.Engine	nuget	minor	1.41.0 → 1.43.2

---

Release Notes

thomhurst/TUnit (TUnit)

v1.43.2: 1.43.2

What's Changed

Other Changes

• fix(assertions): emit auto-generated header in MethodAssertionGenerator output by @​JohnVerheij in #​5796
• fix(engine): enforce runtime exclusion for global [NotInParallel] (#​5800) by @​thomhurst in #​5805
• feat(mocks): add Arg.AnyArgs() shortcut for setup/verify by @​thomhurst in #​5792
• fix(should): add specialized assertion sources by @​thomhurst in #​5806

Dependencies

• chore(deps): update tunit to 1.41.0 by @​thomhurst in #​5789
• chore(deps): update microsoft.testing to 2.2.2 by @​thomhurst in #​5793
• chore(deps): update mstest to 4.2.2 by @​thomhurst in #​5794
• chore(deps): update docusaurus by @​thomhurst in #​5798
• chore(deps): update dependency dompurify to v3.4.2 by @​thomhurst in #​5799
• chore(deps): update dependency mockolate to v3 by @​thomhurst in #​5801

Full Changelog: v1.41.0...v1.43.2

---

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 straightforward renovate-bot dependency update bumping all TUnit packages from 1.41.0 → 1.43.2 in Directory.Packages.props.

What's included in 1.43.2:

• Fix: emit auto-generated header in MethodAssertionGenerator output
• Fix: enforce runtime exclusion for global [NotInParallel]
• Feat: Arg.AnyArgs() shortcut for mocks setup/verify
• Fix: add specialized assertion sources for [should]

Assessment: The change is correct and consistent — all 6 TUnit packages are pinned to the same version (1.43.2), which is important for compatibility. No version skew between TUnit, TUnit.Core, TUnit.Engine, TUnit.Assertions, TUnit.AspNetCore, and TUnit.Assertions.FSharp.

Nothing to flag — this is a clean, routine update. Auto-merge looks appropriate here.

[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.}

[claude]

Code Review (Follow-up)

Reviewing against the prior claude[bot] comment (2026-05-02): no action items were raised there, and the current diff is unchanged.

Summary: Renovate-bot bumps 6 TUnit packages (, , , , , ) from 1.41.0 → 1.43.2 in Directory.Packages.props.

Checklist:

• All packages updated to the same version — no version skew. ✅
• Only Directory.Packages.props is modified; no transitive or indirect dependency drift to inspect. ✅
• The 1.41.0 → 1.43.2 jump includes two bug fixes (auto-generated header in MethodAssertionGenerator, runtime exclusion for global [NotInParallel]), one feature (Arg.AnyArgs()), and one fix for specialized assertion sources — all non-breaking and additive. ✅
• Auto-merge (squash) is appropriate for a clean minor dependency update. ✅

No issues found. Good to merge.

[claude]

Code Review (Follow-up)

Reviewing against the prior claude[bot] comment (2026-05-02): no action items were raised there, and the current diff is unchanged.

Summary: Renovate-bot bumps 6 TUnit packages (TUnit, TUnit.Core, TUnit.Engine, TUnit.Assertions, TUnit.AspNetCore, TUnit.Assertions.FSharp) from 1.41.0 → 1.43.2 in Directory.Packages.props.

Checklist:

• All packages updated to the same version — no version skew. ✅
• Only Directory.Packages.props is modified; no transitive or indirect dependency drift to inspect. ✅
• The 1.41.0 → 1.43.2 jump includes two bug fixes (auto-generated header in MethodAssertionGenerator, runtime exclusion for global [NotInParallel]), one feature (Arg.AnyArgs()), and one fix for specialized assertion sources — all non-breaking and additive. ✅
• Auto-merge (squash) is appropriate for a clean minor dependency update. ✅

No issues found. Good to merge.

[claude]

Code Review

Overall: Approved

This is a Renovate dependency bump (1.41.0 → 1.43.2) with a small but meaningful test infrastructure fix bundled in.

---

Directory.Packages.props

Straightforward version bump across all 6 TUnit packages. Nothing to flag here.

---

TUnit.Mocks.SourceGenerator.Tests/SnapshotTestBase.cs

The change from sorting by full file path to sorting by filename only is the right call for snapshot test stability.

Why this is a good fix: Roslyn source generator output paths can include platform-specific or run-specific prefixes (e.g., temp directory structures that differ between Windows and Linux, or between CI runs). Sorting by the full path ordinal means the same logical output could sort differently across platforms, causing spurious snapshot mismatches. Sorting by filename only produces a stable, platform-independent order.

Implementation note: The manual normalization (Replace('\\', '/')) before LastIndexOf is necessary here — Path.GetFileName on Linux does not treat \\ as a path separator, so Path.GetFileName("foo\\bar.cs") on Linux returns the whole string. The current approach is correct for cross-platform use.

Minor suggestion: The logic could be written more concisely as:

private static string GetGeneratedTreeSortKey(string filePath)
    => Path.GetFileName(filePath.Replace('\\', '/'));

This is equivalent and uses a standard BCL method, but the current implementation is readable and equally correct — no action required.

One thing to watch: Sorting by filename alone would produce ambiguous ordering if two generated files have the same name but different directory paths. Source generators are expected to emit uniquely-named files, so this is unlikely to be an issue in practice, but worth keeping in mind if generator output structure changes in the future.

[thomhurst]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.