chore(deps): update tunit to 0.52.60

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	0.52.56 -> 0.52.60
TUnit.Assertions	nuget	patch	0.52.56 -> 0.52.60
TUnit.Assertions.FSharp	nuget	patch	0.52.56 -> 0.52.60
TUnit.Core	nuget	patch	0.52.56 -> 0.52.60
TUnit.Playwright	nuget	patch	0.52.56 -> 0.52.60

---

Release Notes

thomhurst/TUnit (TUnit)

v0.52.60: 0.52.60

What's Changed

🏕 Changes

• Fix File Paths in the Source Generator by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2823

👒 Dependencies

• chore(deps): update tunit to 0.52.56 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2820
• chore(deps): update dependency enumerableasyncprocessor to v3 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2822
• chore(deps): update dependency enumerableasyncprocessor to 3.0.1 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2824

Full Changelog: v0.52.56...v0.52.60

---

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 PR Review

I've completed a comprehensive review of this dependency update from TUnit 0.52.56 to 0.52.60.

✅ Review Summary

Overall Assessment: APPROVED - This is a safe, well-executed dependency update with no concerns identified.

📋 Code Quality & Best Practices

• ✅ Consistent Updates: All 5 TUnit packages updated uniformly across 10 files
• ✅ Central Package Management: Properly uses Directory.Packages.props for version control
• ✅ Template Consistency: All project templates updated to maintain consistency
• ✅ Version Alignment: No version mismatches between related packages

🐛 Potential Issues

• ✅ No Breaking Changes: This is a patch version update (0.52.56 → 0.52.60)
• ✅ Release Notes: Primary change is "Fix File Paths in the Source Generator" - a bug fix
• ✅ Dependency Conflicts: No conflicting version requirements identified
• ✅ Template Integrity: All template project files maintain proper structure

⚡ Performance Considerations

• ✅ No Performance Impact: Source generator file path fix should improve build reliability
• ✅ Build Optimization: Central package management reduces dependency resolution overhead

🔒 Security Concerns

• ✅ Patch Update Only: Minor version increment with no API surface changes
• ✅ Same Package Source: All packages from the same trusted publisher (thomhurst/TUnit)
• ✅ No New Dependencies: Update doesn't introduce additional dependencies

🧪 Test Coverage Impact

• ✅ Template Coverage: Updates include test project templates ensuring new projects use correct versions
• ✅ NuGet Tester: Tool project also updated to maintain test consistency
• ✅ Build Pipeline: No changes to test execution or coverage requirements

📝 Detailed Changes Analysis

Files updated consistently:

• Directory.Packages.props: Central version definitions (lines 87-89)
• Template projects (9 files): Version references in PackageReference elements
• NuGet tester: Version override updated for validation

All changes are purely version number updates with no structural modifications.

🎯 Recommendations

• ✅ Safe to Merge: This update poses no risks and fixes source generator issues
• ✅ Automated Testing: CI pipeline should validate all templates build correctly
• ✅ No Manual Testing Required: Patch-level updates with bug fixes are low-risk

---

Verdict: This is an exemplary dependency update PR - clean, consistent, and safe to merge.

---

[claude]

Claude finished @thomhurst's task —— View job

---

TUnit Dependency Update PR Review

Reviewing this dependency update from TUnit 0.52.56 to 0.52.60...

Todo List

• Examine changed files and dependency versions
• Analyze code quality and best practices
• Check for potential bugs or issues
• Evaluate performance considerations
• Review security concerns
• Assess test coverage impact

✅ Code Quality & Best Practices

Consistent Version Management: This PR demonstrates excellent dependency management practices:

• All 5 TUnit packages (TUnit, TUnit.Core, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Playwright) are updated uniformly from 0.52.56 to 0.52.60
• Central package management through Directory.Packages.props (lines 87-89) ensures version consistency
• All template projects maintain proper structure and reference the correct versions
• No version mismatches between related packages

Template Consistency: All project templates across different scenarios (ASP.NET, Aspire, F#, Playwright, VB.NET) are consistently updated, maintaining template integrity.

✅ Potential Bugs or Issues

No Breaking Changes: This is a patch version update (0.52.56 → 0.52.60), which follows semantic versioning indicating bug fixes only.

Primary Fix: The release notes mention "Fix File Paths in the Source Generator" as the main change - this is actually a beneficial bug fix that should improve build reliability.

Dependency Alignment: All TUnit-related packages move together, preventing potential compatibility issues between different versions of the same library suite.

✅ Performance Considerations

Source Generator Improvement: The file path fix in the source generator should improve build performance and reliability by ensuring correct file resolution.

Central Package Management Benefits: Using Directory.Packages.props reduces dependency resolution overhead during builds compared to individual package references.

No Performance Regression Risk: Patch-level updates typically don't introduce performance changes, focusing instead on bug fixes.

✅ Security Concerns

Trusted Source: All packages are from the same publisher (thomhurst/TUnit) - no third-party dependencies introduced.

Patch Update Safety: Minor version increments (0.52.56 → 0.52.60) pose minimal security risk as they typically contain bug fixes rather than new attack surfaces.

No New Dependencies: The update doesn't introduce additional dependencies that could expand the attack surface.

Same Package Ecosystem: All updated packages are part of the same TUnit ecosystem, maintaining security consistency.

✅ Test Coverage Impact

Template Coverage: Updates include test project templates, ensuring new projects created from templates use the correct versions.

NuGet Tester Updated: The version override in tools/tunit-nuget-tester/TUnit.NugetTester/TUnit.NugetTester.FSharp/TUnit.NugetTester.FSharp.fsproj:18 ensures testing tools validate the new version.

Build Pipeline Validation: CI pipeline should validate all templates build correctly with the new versions.

Comprehensive Coverage: All TUnit-related components (core, assertions, F# bindings, Playwright integration) are updated together, maintaining test consistency across the entire ecosystem.

🎯 Final Assessment

APPROVED - This is a clean, well-executed dependency update with excellent practices:

• Consistent version management across all related packages
• Safe patch-level updates with beneficial bug fixes
• No security or performance concerns
• Comprehensive template coverage
• Proper central package management

The source generator file path fix should improve build reliability, making this update beneficial for the project.

---