chore(deps): update tunit to 0.61.13

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	0.61.6 -> 0.61.13
TUnit.Assertions	nuget	patch	0.61.6 -> 0.61.13
TUnit.Assertions.FSharp	nuget	patch	0.61.6 -> 0.61.13
TUnit.Core	nuget	patch	0.61.6 -> 0.61.13
TUnit.Playwright	nuget	patch	0.61.6 -> 0.61.13

---

Release Notes

thomhurst/TUnit (TUnit)

v0.61.13: 0.61.13

What's Changed

🏕 Changes

• fix: improve file writing logic with retry mechanism for locked files by @​thomhurst in #​3160
• fix: False positive Missing TimeoutAttribute cancellation token param… by @​thomhurst in #​3162
• fix: disable warnings in auto-generated code by @​thomhurst in #​3163
• fix: add WithMessageNotContaining assertion for exception messages by @​thomhurst in #​3165
• feat: add parsing assertions for various types with format provider support by @​thomhurst in #​3164

👒 Dependencies

• chore(deps): update tunit to 0.61.6 by @​thomhurst in #​3161

Full Changelog: v0.61.6...v0.61.13

---

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

---

Code Review for TUnit Dependency Update

Completed comprehensive review of this Renovate PR that updates TUnit packages from 0.61.6 to 0.61.13.

Todo List:

• Review package version updates for consistency
• Analyze changed files for potential issues
• Check release notes for breaking changes
• Assess security and performance implications
• Verify template file updates
• Provide final review feedback

---

Review Summary: ✅ APPROVED

This is a well-executed dependency update with no concerns identified.

Analysis Results:

✅ Code Quality & Consistency

• All TUnit package versions are consistently updated to 0.61.13
• Version updates properly propagated to all template projects
• Central package management via Directory.Packages.props maintained correctly
• No manual version references left behind

✅ Security Assessment

• Low Risk: Patch version update (0.61.6 → 0.61.13) from same repository
• All packages originate from the trusted TUnit repository
• Release notes show only bug fixes and feature additions, no security patches needed

✅ Performance Considerations

• Positive Impact: Release includes "improve file writing logic with retry mechanism for locked files" (v0.61.13)
• No breaking changes or performance regressions mentioned in release notes
• Framework's performance-first philosophy maintained

✅ Template File Updates

All 8 template files correctly updated:

• TUnit.Templates/content/TUnit/TestProject.csproj: 0.61.6 → 0.61.13
• TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj: TUnit + TUnit.Assertions.FSharp updated
• TUnit.Templates/content/TUnit.Playwright/TestProject.csproj: TUnit.Playwright updated
• Other templates (AspNet, Aspire, VB) similarly updated

✅ Backward Compatibility

• Patch version update maintains API compatibility
• No breaking changes in release notes (0.61.6 → 0.61.13)
• Template consumers will benefit from bug fixes automatically

Release Notes Highlights:

• Bug Fixes: File writing retry mechanism, timeout attribute false positives, auto-generated code warnings
• New Features: WithMessageNotContaining assertion, parsing assertions with format provider support
• No Security Issues: No security-related fixes mentioned

Recommendations:

1. ✅ Merge Approved: This update is safe to merge
2. 📋 Testing: While not required for patch updates, running the test suite (dotnet test) would provide extra confidence
3. 🔄 Automerge: The PR is configured for automerge, which is appropriate for this type of update

Summary: This Renovate PR demonstrates best practices for dependency management. All package versions are consistent, template files are properly maintained, and the changes include beneficial bug fixes and features with no compatibility concerns.