[thomhurst]

This PR contains the following updates:

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

---

Release Notes

thomhurst/TUnit (TUnit)

v0.52.49: 0.52.49

What's Changed

🏕 Changes

• Fix source generated code indentation by properly handling CodeWriter initialization and multi-line object assignments by @​Copilot in https://github.com/thomhurst/TUnit/pull/2807
• feat: Add parallel initialization for injected properties at the same level by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2811

Full Changelog: v0.52.47...v0.52.49

v0.52.47: 0.52.47

What's Changed

🏕 Changes

• Allow DisplayNameAttribute on classes with parameter substitution support by @​Copilot in https://github.com/thomhurst/TUnit/pull/2705
• Make MappableResultAssertionBuilder constructors public for third-party extensibility by @​Copilot in https://github.com/thomhurst/TUnit/pull/2719
• Fix params array argument handling in source generator by @​Copilot in https://github.com/thomhurst/TUnit/pull/2789
• Tidy up analyzer releases: improve organization, documentation, and merge main branch by @​Copilot in https://github.com/thomhurst/TUnit/pull/2712
• Add support for TUNIT_DISABLE_GITHUB_REPORTER environment variable by @​Copilot in https://github.com/thomhurst/TUnit/pull/2716
• Fix TUnit0001 analyzer to use ITypedDataSourceAttribute interface detection by @​Copilot in https://github.com/thomhurst/TUnit/pull/2803
• Fix DependsOn tests to be skipped instead of failed when dependencies fail by @​Copilot in https://github.com/thomhurst/TUnit/pull/2706
• Fix missing --detailed-stacktrace option since v0.50.0 by @​Copilot in https://github.com/thomhurst/TUnit/pull/2808

👒 Dependencies

• chore(deps): update microsoft.testing to 1.8.1 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2690
• chore(deps): update tunit to 0.52.30 by @​thomhurst in https://github.com/thomhurst/TUnit/pull/2802

Full Changelog: v0.52.30...v0.52.47

---

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.30 → 0.52.49

Review Checklist:

• Read repository guidelines (CLAUDE.md) - No repo-specific guidelines found
• Analyze changed files and version consistency
• Review release notes for breaking changes and security implications
• Check package reference patterns and best practices
• Assess potential compatibility issues
• Provide comprehensive review feedback

---

🔍 Review Summary

This is a clean and well-managed dependency update that updates TUnit packages from 0.52.30 to 0.52.49. The changes are consistent and follow best practices.

✅ Positive Findings

Code Quality & Best Practices

• Excellent centralized package management: Uses Directory.Packages.props with ManagePackageVersionsCentrally enabled
• Consistent version updates: All TUnit packages (TUnit, TUnit.Core, TUnit.Assertions, TUnit.Assertions.FSharp, TUnit.Playwright) are updated uniformly to 0.52.49
• Template consistency: All project templates properly reference the updated versions
• Multi-framework support: Testing infrastructure supports multiple target frameworks (net6.0, net8.0, net9.0, net462, net472, net48, net481)

Version Management

• ✅ Directory.Packages.props:87-89 - Central package versions properly updated
• ✅ All template project files consistently use version 0.52.49
• ✅ No version mismatches detected across the codebase

📋 Release Notes Analysis

The update includes several beneficial improvements:

🚀 New Features

• Parallel initialization for injected properties at the same level (performance improvement)
• DisplayNameAttribute support on classes with parameter substitution
• TUNIT_DISABLE_GITHUB_REPORTER environment variable support

🐛 Bug Fixes

• Fixed source generated code indentation issues
• Fixed params array argument handling in source generator
• Fixed DependsOn tests to be skipped instead of failed when dependencies fail
• Fixed missing --detailed-stacktrace option since v0.50.0
• Fixed TUnit0001 analyzer to use ITypedDataSourceAttribute interface detection

🔧 Improvements

• Made MappableResultAssertionBuilder constructors public for third-party extensibility
• Improved analyzer organization and documentation

🔒 Security Assessment

• No security vulnerabilities identified in the release notes
• No breaking changes that would affect security posture
• All changes are backward compatible patch updates

⚡ Performance Considerations

• Positive impact: New parallel initialization feature should improve test startup performance
• Source generation improvements: Better code generation and indentation fixes may have minor positive performance impacts

🧪 Test Coverage

• No test changes required: This is a dependency update with backward compatibility
• Template coverage: All major project templates (C#, F#, AspNet, Playwright, Aspire) are properly updated
• The release includes extensive bug fixes that suggest robust testing of the framework itself

🎯 Recommendations

1. ✅ Approve and merge: This is a well-managed, safe dependency update
2. ✅ Automated testing: The changes should be validated by your existing CI/CD pipeline
3. ✅ Monitor: Keep an eye on the next releases as TUnit continues rapid development

💡 Notable Technical Details

• Uses VersionOverride pattern in TUnit.NugetTester.FSharp.fsproj:18 - good practice for conditional versioning
• Consistent use of OutputType>Exe</OutputType> across test project templates
• Proper support for both .NET Framework and .NET Core/5+ targets

---

Overall Assessment: This is an exemplary dependency update PR. The version management is professional, changes are consistent across all affected files, and the release notes indicate meaningful improvements without breaking changes.

---