chore(deps): update tunit to 0.52.30

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	patch	0.52.25 -> 0.52.30
TUnit.Assertions	nuget	patch	0.52.25 -> 0.52.30
TUnit.Assertions.FSharp	nuget	patch	0.52.25 -> 0.52.30
TUnit.Core	nuget	patch	0.52.25 -> 0.52.30
TUnit.Playwright	nuget	patch	0.52.25 -> 0.52.30

---

Release Notes

thomhurst/TUnit (TUnit)

v0.52.30: 0.52.30

What's Changed

🏕 Changes

• Fully qualify more types in source generated code to avoid namespace clashes by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2797
• Fix TestContext.Configuration by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2796

👒 Dependencies

• chore(deps): update tunit to 0.52.24 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2793
• chore(deps): update tunit to 0.52.25 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2795
• chore(deps): update dependency dotnet-sdk to v9.0.304 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2788

Full Changelog: v0.52.25...v0.52.30

---

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 ✅

This dependency update from TUnit 0.52.25 to 0.52.30 appears to be well-executed and safe to merge.

Code Quality & Best Practices ✅

• Consistent Updates: All TUnit package references have been systematically updated across all affected files
• Central Package Management: Proper use of Directory.Packages.props for centralized version management
• Template Consistency: All project templates (C#, F#, VB.NET, ASP.NET, Playwright, Aspire) updated uniformly
• No Stray References: Verification confirms no old version references (0.52.25) remain in the codebase

Potential Issues ✅

• No Breaking Changes: Based on the release notes, version 0.52.30 contains bug fixes and improvements:
  • Fully qualified types in source-generated code to avoid namespace clashes
  • Fix for TestContext.Configuration
• Version Compatibility: All updated packages maintain version alignment (0.52.30 across TUnit, TUnit.Core, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Playwright)

Performance Considerations ✅

• Performance Impact: The release notes indicate this is a patch release focused on bug fixes rather than performance changes
• Source Generation: Improvements to fully qualify types in generated code should actually reduce potential compilation issues

Security Concerns ✅

• Patch Release: This is a minor patch update (0.52.25 → 0.52.30) with low security risk
• Known Package: TUnit is a well-maintained testing framework by the repository owner
• No New Dependencies: The update doesn't introduce any new dependencies

Test Coverage ✅

• Template Testing: All project templates include proper test configurations
• Consistent Coverage: F# templates correctly include both TUnit and TUnit.Assertions.FSharp packages
• Build System: Updates include nuget tester configurations to validate the new versions

Summary

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

• ✅ Fixes namespace collision issues in source-generated code
• ✅ Resolves TestContext.Configuration problems
• ✅ Maintains consistent versioning across all TUnit packages
• ✅ Updates all templates and tools appropriately
• ✅ Introduces no breaking changes or security concerns

Recommendation: Approve and merge - This is a safe patch update that improves code generation reliability.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: TUnit Dependency Update ✅

This dependency update from TUnit 0.52.25 to 0.52.30 appears to be well-executed and safe to merge.

Code Quality & Best Practices ✅

• Consistent Updates: All TUnit package references have been systematically updated across all affected files
• Central Package Management: Proper use of Directory.Packages.props for centralized version management at /home/runner/work/TUnit/TUnit/Directory.Packages.props:87-89
• Template Consistency: All project templates (C#, F#, VB.NET, ASP.NET, Playwright, Aspire) updated uniformly
• No Stray References: Verification confirms no old version references (0.52.25) remain in the codebase

Potential Issues ✅

• No Breaking Changes: Based on the release notes, version 0.52.30 contains bug fixes and improvements:
  • Fully qualified types in source-generated code to avoid namespace clashes
  • Fix for TestContext.Configuration
• Version Compatibility: All updated packages maintain version alignment (0.52.30 across TUnit, TUnit.Core, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Playwright)

Performance Considerations ✅

• Performance Impact: The release notes indicate this is a patch release focused on bug fixes rather than performance changes
• Source Generation: Improvements to fully qualify types in generated code should actually reduce potential compilation issues

Security Concerns ✅

• Patch Release: This is a minor patch update (0.52.25 → 0.52.30) with low security risk
• Known Package: TUnit is a well-maintained testing framework by the repository owner
• No New Dependencies: The update doesn't introduce any new dependencies

Test Coverage ✅

• Template Testing: All project templates include proper test configurations
• Consistent Coverage: F# templates correctly include both TUnit and TUnit.Assertions.FSharp packages
• Build System: Updates include nuget tester configurations to validate the new versions

Summary

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

• ✅ Fixes namespace collision issues in source-generated code
• ✅ Resolves TestContext.Configuration problems
• ✅ Maintains consistent versioning across all TUnit packages
• ✅ Updates all templates and tools appropriately
• ✅ Introduces no breaking changes or security concerns

Recommendation: Approve and merge - This is a safe patch update that improves code generation reliability.

---