chore(deps): update tunit to 0.79.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	0.78.0 -> 0.79.0
TUnit.Assertions	nuget	minor	0.78.0 -> 0.79.0
TUnit.Assertions.FSharp	nuget	minor	0.78.0 -> 0.79.0
TUnit.Core	nuget	minor	0.78.0 -> 0.79.0
TUnit.Playwright	nuget	minor	0.78.0 -> 0.79.0

---

Release Notes

thomhurst/TUnit (TUnit)

v0.79.0: 0.79.0

What's Changed

Breaking Changes 🛠

• Remove deprecated/obsolete APIs by @​thomhurst in #​3560

🏕 Changes

• Register dynamic test variants at runtime for more flexible testing paradigms (e.g. Property-based Testing) by @​thomhurst in #​3556
• Fix various documentation snippets by @​thomhurst in #​3555
• Add more assertions documentation by @​thomhurst in #​3557
• Add test for negative category filter behavior with explicit tests by @​thomhurst in #​3559
• feat: add more regex assertions by @​thomhurst in #​3558
• feat: add source-generated assertions for various types using AssertionFrom attributes by @​thomhurst in #​3562

👒 Dependencies

• chore(deps): update dependency verify to 31.1.0 by @​thomhurst in #​3549
• chore(deps): update tunit by @​thomhurst in #​3551
• chore(deps): update tunit to 0.78.0 by @​thomhurst in #​3553

Full Changelog: v0.78.0...v0.79.0

---

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

---

Pull Request Review: TUnit 0.78.0 → 0.79.0 Update

Review Checklist

• Analyze changed files and version updates
• Review TUnit 0.79.0 release notes for breaking changes
• Check for potential compatibility issues
• Assess security and performance implications
• Provide comprehensive feedback

Analysis of Changes

Files Changed:

• Directory.Packages.props: TUnit packages updated from 0.78.0 → 0.79.0 (lines 86-88)
• Template project files: Version references updated across 8 template projects

All changes are straightforward version number updates with no logic changes.

Breaking Changes Assessment

⚠️ CRITICAL: Breaking Changes Detected in TUnit 0.79.0

The release notes indicate breaking changes in this version:

• "Remove deprecated/obsolete APIs" - This could potentially break existing code that relies on deprecated APIs

Review Findings

✅ Code Quality & Best Practices

• GOOD: All version updates are consistent across packages
• GOOD: Uses centralized package management via Directory.Packages.props
• GOOD: Template projects maintain consistency with core package versions

⚠️ Potential Issues

1. Breaking Changes Risk: The removal of deprecated/obsolete APIs could break existing code
2. Missing Compatibility Testing: This is a self-referential update (TUnit testing itself with new TUnit version)
3. Template Consistency: All templates should be tested to ensure they work with the new version

✅ Security & Performance

• GOOD: Dependency updates often include security fixes
• GOOD: No performance-critical changes in version updates themselves
• GOOD: New regex assertions and source-generated assertions may improve performance

❌ Test Coverage Concerns

• MISSING: Cannot verify if existing tests pass with new version (requires testing approval)
• RECOMMENDATION: Run full test suite before merging to ensure no breaking changes affect this codebase

Recommendations

1. BEFORE MERGING: Run the full test suite to verify compatibility:

   dotnet test

2. Check for Deprecated API Usage: Search codebase for any deprecated TUnit APIs that may have been removed:

   # Look for potentially deprecated patterns in test files
   grep -r "ObsoleteAttribute\|DeprecatedAttribute" . --include="*.cs"

3. Template Testing: Verify all template projects can be created and run successfully

4. Consider Gradual Rollout: Given the breaking changes, consider testing on a subset of projects first

Summary

This appears to be a low-risk update since:

• Only version numbers are changed
• This is the TUnit repository updating its own dependencies
• Recent commits show active development and testing

However, the breaking changes in 0.79.0 require validation that no deprecated APIs are being used in the current codebase.

Recommendation: ✅ APPROVE after running tests to ensure no breaking changes affect this repository.

---