chore(deps): update tunit to 0.77.3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	0.77.0 -> 0.77.3
TUnit.Assertions	nuget	patch	0.77.0 -> 0.77.3
TUnit.Assertions.FSharp	nuget	patch	0.77.0 -> 0.77.3
TUnit.Core	nuget	patch	0.77.0 -> 0.77.3
TUnit.Playwright	nuget	patch	0.77.0 -> 0.77.3

---

Release Notes

thomhurst/TUnit (TUnit)

v0.77.3: 0.77.3

What's Changed

🏕 Changes

• analyzer: include referenced assemblies when retrieving all named types in compilation by @​thomhurst in #​3529
• perf: optimize asynchronous event handling with lock-free operations and immutable collections by @​thomhurst in #​3535

👒 Dependencies

• chore(deps): update tunit to 0.77.0 by @​thomhurst in #​3534

Full Changelog: v0.77.0...v0.77.3

---

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

---

TUnit Dependency Update Review

Reviewing this automated dependency update from TUnit 0.77.0 → 0.77.3.

Review Checklist

• Analyze changed files and version consistency
• Review Directory.Packages.props for centralized dependency management
• Check template project files for proper updates
• Evaluate release notes for breaking changes or security issues
• Assess performance implications from release notes
• Provide comprehensive review feedback

---

Review Findings

✅ Code Quality & Best Practices

• Excellent centralized dependency management: The use of Directory.Packages.props with ManagePackageVersionsCentrally follows best practices
• Consistent version updates: All TUnit packages are properly updated from 0.77.0 → 0.77.3 across:
  • Directory.Packages.props:86-88 (TUnit, TUnit.Core, TUnit.Assertions)
  • All template project files consistently reference the new versions
• Clean automated update: Renovate correctly identified and updated all package references

✅ Version Consistency

All TUnit packages are updated uniformly:

• TUnit: 0.77.0 → 0.77.3
• TUnit.Core: 0.77.0 → 0.77.3
• TUnit.Assertions: 0.77.0 → 0.77.3
• TUnit.Assertions.FSharp: 0.77.0 → 0.77.3
• TUnit.Playwright: 0.77.0 → 0.77.3

✅ Performance Considerations

Based on the release notes, this update includes performance improvements:

• Lock-free operations: "optimize asynchronous event handling with lock-free operations and immutable collections" (perf: optimize asynchronous event handling with lock-free operations and immutable collections #3535)
• Analyzer improvements: "include referenced assemblies when retrieving all named types in compilation" (analyzer: include referenced assemblies when retrieving all named types in compilation #3529)

These changes should provide performance benefits with no negative impact.

✅ Security Assessment

• Patch version update: This is a patch release (0.77.0 → 0.77.3), indicating bug fixes and improvements without breaking changes
• No security vulnerabilities noted: Release notes don't mention any security fixes, but patch updates often include stability improvements
• Trusted source: Updates are from the official TUnit repository

⚠️ Potential Issues

1. Inconsistent F# package version: I noticed TUnit.Assertions.FSharp is still on version 0.75.38-PullRequest3485.0 in Directory.Packages.props:83, while the template files use 0.77.3. This may be intentional for testing, but should be verified.

2. Template coverage: The update covers major template scenarios (C#, F#, VB.NET, AspNet, Aspire, Playwright) but ensure any other consuming projects also get updated.

✅ Test Coverage

• No test changes required: This is purely a dependency version bump
• Templates maintain structure: All project templates maintain their structure and only version numbers changed
• Centralized management reduces risk: Using Directory.Packages.props minimizes the chance of version mismatches

Recommendation: ✅ APPROVE

This is a clean, well-managed dependency update that:

• Follows the project's established dependency management patterns
• Includes beneficial performance improvements
• Maintains version consistency across all packages
• Poses minimal risk as a patch-level update
• Is automatically managed by Renovate with proper configuration

The only minor concern is the F# package version inconsistency, but this appears to be intentional for development purposes.

---