chore(deps): update tunit to 0.52.51

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	0.52.49 -> 0.52.51
TUnit.Assertions	nuget	patch	0.52.49 -> 0.52.51
TUnit.Assertions.FSharp	nuget	patch	0.52.49 -> 0.52.51
TUnit.Core	nuget	patch	0.52.49 -> 0.52.51
TUnit.Playwright	nuget	patch	0.52.49 -> 0.52.51

---

Release Notes

thomhurst/TUnit (TUnit)

v0.52.51: 0.52.51

What's Changed

🏕 Changes

• Fix missing namespace issues in TestMetadataGenerator generated code by @​Copilot in https://github.com/thomhurst/TUnit/pull/2814

👒 Dependencies

• chore(deps): update tunit to 0.52.49 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2812

Full Changelog: v0.52.49...v0.52.51

---

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 0.52.49 → 0.52.51

Completed comprehensive review of this automated dependency update PR.

Review Checklist

• Read repository guidelines (CLAUDE.md)
• Examine all changed files for consistency
• Analyze version changes and release notes
• Check for potential issues or breaking changes
• Evaluate security implications
• Assess performance considerations
• Review test coverage impact
• Provide comprehensive feedback

---

📋 Review Summary

This is a low-risk, automated patch version update that appears safe to merge.

📦 Changes Overview

Packages Updated:

• TUnit: 0.52.49 → 0.52.51
• TUnit.Core: 0.52.49 → 0.52.51
• TUnit.Assertions: 0.52.49 → 0.52.51
• TUnit.Assertions.FSharp: 0.52.49 → 0.52.51
• TUnit.Playwright: 0.52.49 → 0.52.51

Files Modified: 10 files (all project/template files)

✅ Code Quality & Best Practices

Excellent:

• ✅ Consistent version updates across all files
• ✅ Uses centralized package management (Directory.Packages.props)
• ✅ All template files maintain proper structure
• ✅ Version updates follow semantic versioning (patch level)

Notable:

• The repository uses centralized package version management through Directory.Packages.props:87-89, which is a best practice for multi-project solutions
• Template files in TUnit.Templates/content/ are properly updated to reflect the new version
• F# project files correctly update both TUnit and TUnit.Assertions.FSharp packages

🐛 Potential Issues Assessment

Low Risk:

• This is a patch version update (0.52.49 → 0.52.51), indicating bug fixes only
• According to the release notes, the main change is: "Fix missing namespace issues in TestMetadataGenerator generated code"
• No breaking changes expected in patch releases

No Issues Found:

• All version references are consistently updated
• No dependency conflicts detected
• Template structure remains intact

🚀 Performance Considerations

Neutral Impact:

• Patch updates typically contain performance improvements or bug fixes
• The "missing namespace issues" fix suggests improved code generation, which could have positive performance implications
• No performance regressions expected from this update

🔒 Security Assessment

Low Security Risk:

• This is a first-party dependency update (same maintainer/organization)
• Patch version updates have minimal security surface area changes
• No security advisories noted in the release
• Updates are from a trusted, well-maintained testing framework

🧪 Test Coverage Impact

Positive Impact:

• Bug fix for "missing namespace issues in TestMetadataGenerator" likely improves test reliability
• Template consistency ensures generated test projects will work correctly
• No test coverage reduction expected

📝 Specific File Analysis

Directory.Packages.props:87-89

• ✅ Central version management properly updated
• ✅ Consistent with project's dependency management strategy

Template Files (9 files)

• ✅ All template files consistently updated
• ✅ Both C# and F# templates properly maintained
• ✅ Specialized templates (AspNet, Aspire, Playwright, VB) all updated

NuGet Tester (tools/tunit-nuget-tester/)

• ✅ Test tooling updated to match main dependency versions

🎯 Recommendations

✅ APPROVE & MERGE

This PR is:

• Safe to merge - patch version with bug fixes only
• Well-structured - consistent updates across all files
• Low risk - addresses code generation issues
• Maintains quality - follows proper dependency management practices

No action required - the automated checks and consistent version updates demonstrate this is a routine maintenance update that improves the codebase.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: TUnit Dependency Update 0.52.49 → 0.52.51

Completed comprehensive review of this automated dependency update PR.

Review Checklist

• Read repository guidelines (CLAUDE.md)
• Examine all changed files for consistency
• Analyze version changes and release notes
• Check for potential issues or breaking changes
• Evaluate security implications
• Assess performance considerations
• Review test coverage impact
• Provide comprehensive feedback

---

📋 Review Summary

This is a low-risk, automated patch version update that appears safe to merge.

📦 Changes Overview

Packages Updated:

• TUnit: 0.52.49 → 0.52.51
• TUnit.Core: 0.52.49 → 0.52.51
• TUnit.Assertions: 0.52.49 → 0.52.51
• TUnit.Assertions.FSharp: 0.52.49 → 0.52.51
• TUnit.Playwright: 0.52.49 → 0.52.51

Files Modified: 10 files (all project/template files)

✅ Code Quality & Best Practices

Excellent:

• ✅ Consistent version updates across all files
• ✅ Uses centralized package management (Directory.Packages.props)
• ✅ All template files maintain proper structure
• ✅ Version updates follow semantic versioning (patch level)

Notable:

• The repository uses centralized package version management through Directory.Packages.props:87-89, which is a best practice for multi-project solutions
• Template files in TUnit.Templates/content/ are properly updated to reflect the new version
• F# project files correctly update both TUnit and TUnit.Assertions.FSharp packages

🐛 Potential Issues Assessment

Low Risk:

• This is a patch version update (0.52.49 → 0.52.51), indicating bug fixes only
• According to the release notes, the main change is: "Fix missing namespace issues in TestMetadataGenerator generated code"
• No breaking changes expected in patch releases

No Issues Found:

• All version references are consistently updated
• No dependency conflicts detected
• Template structure remains intact

🚀 Performance Considerations

Neutral Impact:

• Patch updates typically contain performance improvements or bug fixes
• The "missing namespace issues" fix suggests improved code generation, which could have positive performance implications
• No performance regressions expected from this update

🔒 Security Assessment

Low Security Risk:

• This is a first-party dependency update (same maintainer/organization)
• Patch version updates have minimal security surface area changes
• No security advisories noted in the release
• Updates are from a trusted, well-maintained testing framework

🧪 Test Coverage Impact

Positive Impact:

• Bug fix for "missing namespace issues in TestMetadataGenerator" likely improves test reliability
• Template consistency ensures generated test projects will work correctly
• No test coverage reduction expected

📝 Specific File Analysis

Directory.Packages.props:87-89

• ✅ Central version management properly updated
• ✅ Consistent with project's dependency management strategy

Template Files (9 files)

• ✅ All template files consistently updated
• ✅ Both C# and F# templates properly maintained
• ✅ Specialized templates (AspNet, Aspire, Playwright, VB) all updated

NuGet Tester (tools/tunit-nuget-tester/)

• ✅ Test tooling updated to match main dependency versions

🎯 Recommendations

✅ APPROVE & MERGE

This PR is:

• Safe to merge - patch version with bug fixes only
• Well-structured - consistent updates across all files
• Low risk - addresses code generation issues
• Maintains quality - follows proper dependency management practices

No action required - the automated checks and consistent version updates demonstrate this is a routine maintenance update that improves the codebase.

---