chore(deps): update tunit to 0.90.42

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	0.90.38 -> 0.90.42
TUnit.Assertions	nuget	patch	0.90.38 -> 0.90.42
TUnit.Assertions.FSharp	nuget	patch	0.90.38 -> 0.90.42
TUnit.Core	nuget	patch	0.90.38 -> 0.90.42
TUnit.Playwright	nuget	patch	0.90.38 -> 0.90.42

---

Release Notes

thomhurst/TUnit (TUnit)

v0.90.42: 0.90.42

What's Changed

🏕 Changes

• feat: enable conditional source generation based on configuration property by @​thomhurst in #​3699
• refactor: adjust parallelism handling in TestScheduler for better resource management by @​thomhurst in #​3701

👒 Dependencies

• chore(deps): update tunit to 0.90.38 by @​thomhurst in #​3698

Full Changelog: v0.90.38...v0.90.42

---

Configuration

📅 Schedule: 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 Renovate Bot.

[claude]

Claude finished @thomhurst's task —— View job

---

Reviewing Dependency Update PR

I'll analyze this dependency update PR and provide feedback on code quality, potential issues, and security considerations.

Todo List:

• Read and analyze changed files
• Review version changes and release notes
• Check for consistency across templates
• Assess potential security/performance impacts
• Provide comprehensive review feedback

---

Review Summary: ✅ APPROVED

This is a clean, well-structured dependency update PR with no issues identified.

Detailed Analysis

Code Quality: Excellent ✅

• Consistency: All template files have been updated uniformly from version 0.90.38 to 0.90.42
• Scope: Updates are properly limited to version numbers only - no functional code changes
• Centralized Management: The main version definitions in Directory.Packages.props follow the centralized package management pattern
• Template Coverage: All 9 template project files updated consistently across different scenarios (C#, F#, VB.NET, ASP.NET, Aspire, Playwright)

Version Update Assessment: Low Risk ✅

• Patch Version: This is a patch version bump (0.90.38 → 0.90.42), indicating backward-compatible bug fixes
• Release Notes Analysis: Based on the provided release notes, this update includes:
  • Feature: conditional source generation based on configuration property (TUnit.Core.SourceGenerator:3699)
  • Refactor: improved parallelism handling in TestScheduler (TUnit.Engine:3701)
• Breaking Changes: None identified - patch versions maintain backward compatibility

Security Considerations: No Concerns ✅

• Package Source: All packages are from the official TUnit repository (thomhurst/TUnit)
• Scope: Version-only changes with no new dependencies introduced
• Supply Chain: Using established, centrally managed packages already in use

Performance Impact: Positive ✅

• Parallelism Improvements: The TestScheduler refactor (refactor: adjust parallelism handling in TestScheduler for better resource management #3701) specifically targets "better resource management"
• Source Generation: New conditional source generation feature may reduce compilation overhead when not needed
• No Performance Regressions: Patch version nature minimizes risk of performance degradation

Test Coverage: Maintained ✅

• Template Integrity: All project templates maintain their existing structure and dependencies
• Consistency Check: Version numbers are consistently updated across all affected files
• No Functional Changes: Since only versions changed, existing test coverage remains valid

Files Updated

• Directory.Packages.props: Central package versions (TUnit, TUnit.Core, TUnit.Assertions: 0.90.38 → 0.90.42)
• Template project files (9 files): Consistent version updates across C#, F#, VB.NET, ASP.NET, Aspire, and Playwright templates

Recommendations

1. Merge Approved: This is a straightforward, low-risk dependency update
2. Automated Testing: The existing CI pipeline should validate template integrity
3. Monitor: Watch for any issues after merge, though none are expected given the patch nature

Final Assessment

This PR demonstrates excellent dependency management practices with consistent, automated updates across all relevant files. The changes are minimal, targeted, and follow proper versioning practices.