chore(deps): update tunit to 0.90.32

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	0.90.28 -> 0.90.32
TUnit.Assertions	nuget	patch	0.90.28 -> 0.90.32
TUnit.Assertions.FSharp	nuget	patch	0.90.28 -> 0.90.32
TUnit.Core	nuget	patch	0.90.28 -> 0.90.32
TUnit.Playwright	nuget	patch	0.90.28 -> 0.90.32

---

Release Notes

thomhurst/TUnit (TUnit)

v0.90.32: 0.90.32

What's Changed

🏕 Changes

• perf: optimize test execution by partitioning tests by @​thomhurst in #​3676
• fix: fix nested classes conflicting with the same testid by @​thomhurst in #​3690

👒 Dependencies

• chore(deps): update tunit to 0.90.28 by @​thomhurst in #​3687
• chore(deps): update docker/setup-docker-action action to v4.5.0 by @​thomhurst in #​3688

Full Changelog: v0.90.28...v0.90.32

---

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

---

PR Review: TUnit Dependency Update to 0.90.32

Todo List:

• Analyze changed files and dependency updates
• Review release notes for breaking changes and security issues
• Check template consistency across all project types
• Assess performance and security implications
• Provide comprehensive review feedback

Review Summary

This PR updates TUnit packages from 0.90.28 to 0.90.32 across template projects. Here's my comprehensive review:

✅ Code Quality & Best Practices

Good:

• ✅ Consistent version updates across all templates
• ✅ Proper use of centralized package management (Directory.Packages.props)
• ✅ All template project files maintain consistent structure and formatting
• ✅ Version updates are applied to the correct package references:
  • TUnit (main package)
  • TUnit.Core (core abstractions)
  • TUnit.Assertions (assertion library)
  • TUnit.Assertions.FSharp (F# assertions)
  • TUnit.Playwright (browser testing)

Template Consistency Analysis:

• ✅ All 9 template files correctly updated to 0.90.32
• ✅ F# templates properly reference both TUnit and TUnit.Assertions.FSharp
• ✅ Playwright template correctly references TUnit.Playwright
• ✅ AspNet templates maintain proper package references

🔍 Potential Issues

Minor Observations:

• 📋 The F# assertion package TUnit.Assertions.FSharp in Directory.Packages.props shows version 0.75.38-PullRequest3485.0 which appears to be a pre-release version from a different PR - this might need attention in the future

🚀 Performance Considerations

Positive Impact:

• ✅ Release notes mention "perf: optimize test execution by partitioning tests" (perf: optimize test execution by partitioning tests #3676)
• ✅ Patch version updates typically don't introduce breaking performance changes
• ✅ Performance optimizations should benefit all template users

🔒 Security Assessment

Security Status:

• ✅ No security vulnerabilities identified in release notes
• ✅ Updates from official TUnit repository (trusted source)
• ✅ Patch version update (0.90.28 → 0.90.32) indicates minimal risk
• ✅ No new dependencies introduced

🧪 Test Coverage

Template Testing:

• ✅ Templates are used by TUnit.Templates.Tests project which should validate template integrity
• ✅ All template project files maintain their testing structure
• ✅ Version updates shouldn't affect test logic in templates

📋 Key Changes from Release Notes

The 0.90.32 release includes:

1. Performance Enhancement: Optimized test execution through test partitioning
2. Bug Fix: Fixed nested classes conflicting with the same test ID
3. Dependencies: Various dependency updates

🏆 Recommendation

✅ APPROVE - This is a well-executed dependency update with:

• Consistent version bumps across all affected templates
• Performance improvements and bug fixes
• No breaking changes or security concerns
• Proper centralized package management

The only minor observation is the pre-release F# assertion package version in Directory.Packages.props, but this doesn't affect the current PR scope.