chore(deps): update tunit to 0.72.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
TUnit	nuget	minor	0.67.19 -> 0.72.0
TUnit.Assertions	nuget	minor	0.67.19 -> 0.72.0
TUnit.Assertions.FSharp	nuget	minor	0.67.19 -> 0.72.0
TUnit.Core	nuget	minor	0.67.19 -> 0.72.0
TUnit.Playwright	nuget	minor	0.67.19 -> 0.72.0

---

Release Notes

thomhurst/TUnit (TUnit)

v0.72.0: 0.72.0

What's Changed

🏕 Changes

• feat: enhance empty collection assertions with detailed failure messages by @​thomhurst in #​3383
• Add IsOrderedBy(Descending) and fix IsTypeOf assertion by @​thomhurst in #​3396
• Fix Assertion Nullability warnings by @​thomhurst in #​3397
• feat: add collection count assertions for GreaterThan, LessThan, LessThanOrEqualTo, Between, Zero, and NotEqualTo by @​thomhurst in #​3398

👒 Dependencies

• chore(deps): update dependency microsoft.templateengine.authoring.templateverifier to 9.0.306 by @​thomhurst in #​3384
• chore(deps): update dependency system.commandline to 2.0.0-rc.2.25502.107 by @​thomhurst in #​3385
• chore(deps): update microsoft.aspnetcore to 9.0.10 by @​thomhurst in #​3388

Full Changelog: v0.71.4...v0.72.0

v0.71.4: 0.71.4

What's Changed

🏕 Changes

• Add generated assertions and extension methods for various constraints by @​thomhurst in #​3386
• feat(tests): add new equality assertions for enums and custom value types by @​thomhurst in #​3390

👒 Dependencies

• chore(deps): update dependency microsoft.templateengine.authoring.cli to v9.0.306 by @​thomhurst in #​3381
• chore(deps): update dependency microsoft.build.utilities.core to 17.14.28 by @​thomhurst in #​3380

Full Changelog: v0.71.0...v0.71.4

v0.71.0: 0.71.0

What's Changed

🏕 Changes

• Support internal classes and properties with ClassDataSource attribute by @​Copilot in #​3370
• feat: add support for generic method assertions with non-inferable type parameters by @​thomhurst in #​3379
• Update Microsoft Testing Platform to v2 by @​thomhurst in #​3375

👒 Dependencies

• chore(deps): update dependency microsoft.entityframeworkcore to 9.0.10 by @​thomhurst in #​3378
• chore(deps): update dependency fsharp.core to 10.0.100-rc2.25502.107 by @​thomhurst in #​3377

Full Changelog: v0.70.7...v0.71.0

v0.70.7: 0.70.7

What's Changed

🏕 Changes

• fix: implement linear search for custom comparers in IsEquivalentToAssertion by @​thomhurst in #​3368
• feat: add support for cross-type equality assertions with IEquatable by @​thomhurst in #​3366

👒 Dependencies

• chore(deps): update mstest to 4.0.1 by @​thomhurst in #​3373

Full Changelog: v0.70.4...v0.70.7

v0.70.4: 0.70.4

What's Changed

🏕 Changes

• Fix overload resolution for IsTypeOf<> and nullable types by @​thomhurst in #​3365

👒 Dependencies

• chore(deps): update actions/setup-node action to v6 by @​thomhurst in #​3364

Full Changelog: v0.70.2...v0.70.4

v0.70.2: 0.70.2

What's Changed

🏕 Changes

• Fix IsEqualTo assertion for double.NaN values by @​Copilot in #​3360

👒 Dependencies

• chore(deps): update dependency publicapigenerator to 11.5.0 by @​thomhurst in #​3361

Full Changelog: v0.70.0...v0.70.2

v0.70.0: 0.70.0

This change focuses on major changes around the assertions API. Those who have defined custom assertions will need to adjust their code to inherit from Assertion<T> now.

There is also source generators to easily define custom assertions - See more here: https://tunit.dev/docs/assertions/extensibility/source-generator-assertions

What's Changed

Breaking Changes 🛠

• Simplify Assertion API by @​thomhurst in #​3324
• Source Generate Assertion Extension Methods by @​thomhurst in #​3354

🏕 Changes

• feat: add NUnit and MSTest migration analyzers and code fixers by @​thomhurst in #​3195
• Enhance Assertion source generation for easier extensibility by @​thomhurst in #​3356

👒 Dependencies

• chore(deps): update dependency verify to 31.0.1 by @​thomhurst in #​3350
• chore(deps): update dependency tunit.playwright to 0.67.19 by @​thomhurst in #​3351
• chore(deps): update tunit to 0.67.19 by @​thomhurst in #​3352
• chore(deps): update dependency verify.nunit to v31 by @​thomhurst in #​3342
• chore(deps): update dependency verify.tunit to v31 by @​thomhurst in #​3344

Full Changelog: v0.67.19...v0.70.0

---

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 0.70.0 Dependency Update

Review Checklist:

• Analyze changed files and version consistency
• Review breaking changes impact
• Check for any missing updates or code adjustments needed
• Assess security and performance implications
• Provide final recommendations

Files Analyzed:

All 9 template project files have been consistently updated from 0.67.19 to 0.70.0. The version updates are clean and consistent across:

• Directory.Packages.props: Core TUnit packages updated
• Template project files: All package references properly updated

Version Consistency: ✅ GOOD

• All TUnit package versions are consistently updated to 0.70.0
• No version mismatches detected
• Central package management in Directory.Packages.props is properly maintained

Breaking Changes Impact Analysis: ✅ LOW RISK

Key Changes in 0.70.0:

• Major: Assertion API simplified - custom assertions must now inherit from Assertion<T>
• New: Source generators for custom assertions
• Addition: NUnit/MSTest migration analyzers

Template Impact Assessment:

• ✅ No custom assertions found in template files - templates only use standard TUnit packages
• ✅ No breaking changes affect templates - they use standard test patterns
• ✅ The disabled custom assertion example (ProblemDetailsAssertion.cs.disabled) uses modern API patterns that should be compatible

Security & Performance: ✅ GOOD

• Security: Minor version bump with no known security vulnerabilities
• Performance: Release includes optimization improvements and new source generators
• Compatibility: All target frameworks remain supported (.NET 6, 8, 9+)

Final Recommendations: ✅ APPROVE

This PR is safe to merge for the following reasons:

1. Clean dependency update: All version references consistently updated
2. No breaking changes for templates: Templates use standard APIs unaffected by breaking changes
3. Low migration risk: Breaking changes only affect custom assertion authors
4. Added value: New migration analyzers will help users transition from other test frameworks
5. Proper testing: This is TUnit's own repository, so comprehensive testing is expected

Auto-merge approval: The Renovate Bot configuration with auto-merge is appropriate for this dependency update since it's a clean version bump without compatibility issues for the template projects.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: TUnit 0.70.0 Dependency Update

Review Checklist:

• Analyze changed files and version consistency
• Review breaking changes impact
• Check for any missing updates or code adjustments needed
• Assess security and performance implications
• Provide final recommendations

Files Analyzed:

All 9 template project files have been consistently updated from 0.67.19 to 0.70.0. The version updates are clean and consistent across:

• Directory.Packages.props: Core TUnit packages updated (lines 84-86)
• Template project files: All package references properly updated

Version Consistency: ✅ GOOD

• All TUnit package versions are consistently updated to 0.70.0
• No version mismatches detected
• Central package management in Directory.Packages.props is properly maintained

Breaking Changes Impact Analysis: ✅ LOW RISK

Key Changes in 0.70.0:

• Major: Assertion API simplified - custom assertions must now inherit from Assertion<T>
• New: Source generators for custom assertions
• Addition: NUnit/MSTest migration analyzers

Template Impact Assessment:

• ✅ No custom assertions found in template files - templates only use standard TUnit packages
• ✅ No breaking changes affect templates - they use standard test patterns like Assert.That(result).IsEqualTo(c)
• ✅ The disabled custom assertion example (ProblemDetailsAssertion.cs.disabled) uses modern API patterns that should be compatible

Security & Performance: ✅ GOOD

• Security: Minor version bump with no known security vulnerabilities
• Performance: Release includes optimization improvements and new source generators
• Compatibility: All target frameworks remain supported (.NET 6, 8, 9+)

Final Recommendations: ✅ APPROVE

This PR is safe to merge for the following reasons:

1. Clean dependency update: All version references consistently updated
2. No breaking changes for templates: Templates use standard APIs unaffected by breaking changes
3. Low migration risk: Breaking changes only affect custom assertion authors
4. Added value: New migration analyzers will help users transition from other test frameworks
5. Proper testing: This is TUnit's own repository, so comprehensive testing is expected

Auto-merge approval: The Renovate Bot configuration with auto-merge is appropriate for this dependency update since it's a clean version bump without compatibility issues for the template projects.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: TUnit 0.70.0 Dependency Update

Review Checklist:

• Analyze changed files and version consistency
• Review breaking changes impact
• Check for any missing updates or code adjustments needed
• Assess security and performance implications
• Provide final recommendations

Files Analyzed:

All 9 template project files have been consistently updated from 0.67.19 to 0.70.0. The version updates are clean and consistent across:

• Directory.Packages.props: Core TUnit packages updated (lines 84-86)
• Template project files: All package references properly updated

Version Consistency: ✅ GOOD

• All TUnit package versions are consistently updated to 0.70.0
• No version mismatches detected
• Central package management in Directory.Packages.props is properly maintained

Breaking Changes Impact Analysis: ✅ LOW RISK

Key Changes in 0.70.0:

• Major: Assertion API simplified - custom assertions must now inherit from Assertion<T>
• New: Source generators for custom assertions
• Addition: NUnit/MSTest migration analyzers

Template Impact Assessment:

• ✅ No custom assertions found in template files - templates only use standard TUnit packages
• ✅ No breaking changes affect templates - they use standard test patterns like Assert.That(result).IsEqualTo(c)
• ✅ All template packages properly updated including TUnit.Playwright and TUnit.Assertions.FSharp

Missing Updates Check: ✅ COMPLETE

Analysis of Package References:

• ✅ TUnit.Playwright updated in template (line 11 in TestProject.csproj)
• ✅ TUnit.Assertions.FSharp updated in F# template (line 14 in TestProject.fsproj)
• ✅ All other TUnit packages consistently updated across templates
• ✅ No missing package updates detected

Note: TUnit.Playwright and TUnit.Assertions.FSharp are not managed centrally in Directory.Packages.props but are correctly updated in their respective template projects.

Security & Performance: ✅ GOOD

• Security: Minor version bump with no known security vulnerabilities
• Performance: Release includes optimization improvements and new source generators
• Compatibility: All target frameworks remain supported (.NET 6, 8, 9+)

Final Recommendations: ✅ APPROVE

This PR is safe to merge for the following reasons:

1. Clean dependency update: All version references consistently updated
2. No breaking changes for templates: Templates use standard APIs unaffected by breaking changes
3. Low migration risk: Breaking changes only affect custom assertion authors
4. Added value: New migration analyzers will help users transition from other test frameworks
5. Proper testing: This is TUnit's own repository, so comprehensive testing is expected

Auto-merge approval: The Renovate Bot configuration with auto-merge is appropriate for this dependency update since it's a clean version bump without compatibility issues for the template projects.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: TUnit 0.70.2 Dependency Update

Review Checklist:

• Analyze changed files and version consistency
• Review breaking changes impact
• Check for any missing updates or code adjustments needed
• Assess security and performance implications
• Provide final recommendations

Files Analyzed:

All 9 template project files have been consistently updated from 0.67.19 to 0.70.2. The version updates are clean and consistent across:

• Directory.Packages.props: Core TUnit packages updated (lines 84-86)
• Template project files: All package references properly updated

Version Consistency: ✅ GOOD

• All TUnit package versions are consistently updated to 0.70.2
• No version mismatches detected
• Central package management in Directory.Packages.props is properly maintained

Breaking Changes Impact Analysis: ✅ LOW RISK

Key Changes in 0.70.0:

• Major: Assertion API simplified - custom assertions must now inherit from Assertion<T>
• New: Source generators for custom assertions
• Addition: NUnit/MSTest migration analyzers

Template Impact Assessment:

• ✅ No custom assertions found in template files - templates only use standard TUnit packages
• ✅ No breaking changes affect templates - they use standard test patterns like Assert.That(result).IsEqualTo(c)
• ✅ All template packages properly updated including TUnit.Playwright and TUnit.Assertions.FSharp

Missing Updates Check: ✅ COMPLETE

Analysis of Package References:

• ✅ TUnit.Playwright updated in template (line 11 in TestProject.csproj)
• ✅ TUnit.Assertions.FSharp updated in F# templates (line 14 in both TestProject.fsproj files)
• ✅ All other TUnit packages consistently updated across templates
• ✅ No missing package updates detected

Note: TUnit.Playwright and TUnit.Assertions.FSharp are not managed centrally in Directory.Packages.props but are correctly updated in their respective template projects.

Security & Performance: ✅ GOOD

• Security: Minor version bump with no known security vulnerabilities
• Performance: Release includes optimization improvements and new source generators
• Compatibility: All target frameworks remain supported (.NET 6, 8, 9+)

Final Recommendations: ✅ APPROVE

This PR is safe to merge for the following reasons:

1. Clean dependency update: All version references consistently updated
2. No breaking changes for templates: Templates use standard APIs unaffected by breaking changes
3. Low migration risk: Breaking changes only affect custom assertion authors
4. Added value: New migration analyzers will help users transition from other test frameworks
5. Proper testing: This is TUnit's own repository, so comprehensive testing is expected

Auto-merge approval: The Renovate Bot configuration with auto-merge is appropriate for this dependency update since it's a clean version bump without compatibility issues for the template projects.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: TUnit 0.70.2 Dependency Update

Review Checklist:

• Analyze changed files and version consistency
• Review breaking changes impact
• Check for any missing updates or code adjustments needed
• Assess security and performance implications
• Provide final recommendations

Files Analyzed:

All 9 template project files have been consistently updated from 0.67.19 to 0.70.2. The version updates are clean and consistent across:

• Directory.Packages.props: Core TUnit packages updated (lines 84-86)
• Template project files: All package references properly updated

Version Consistency: ✅ GOOD

• All TUnit package versions are consistently updated to 0.70.2
• No version mismatches detected
• Central package management in Directory.Packages.props is properly maintained

Breaking Changes Impact Analysis: ✅ LOW RISK

Key Changes in 0.70.0:

• Major: Assertion API simplified - custom assertions must now inherit from Assertion<T>
• New: Source generators for custom assertions
• Addition: NUnit/MSTest migration analyzers

Template Impact Assessment:

• ✅ No custom assertions found in template files - templates only use standard TUnit packages
• ✅ No breaking changes affect templates - they use standard test patterns like Assert.That(result).IsEqualTo(c)
• ✅ All template packages properly updated including TUnit.Playwright and TUnit.Assertions.FSharp

Missing Updates Check: ✅ COMPLETE

Analysis of Package References:

• ✅ TUnit.Playwright updated in template (line 11 in TestProject.csproj)
• ✅ TUnit.Assertions.FSharp updated in F# templates (line 14 in both TestProject.fsproj files)
• ✅ All other TUnit packages consistently updated across templates
• ✅ No missing package updates detected

Note: TUnit.Playwright and TUnit.Assertions.FSharp are not managed centrally in Directory.Packages.props but are correctly updated in their respective template projects.

Security & Performance: ✅ GOOD

• Security: Minor version bump (0.70.2) with no known security vulnerabilities. Includes bug fix for double.NaN handling in assertions.
• Performance: Release includes optimization improvements and new source generators for better compile-time performance
• Compatibility: All target frameworks remain supported (.NET 6, 8, 9+)

Code Quality Assessment: ✅ EXCELLENT

• Best Practices: Clean, consistent version management using central package management
• Test Coverage: Templates use standard assertion patterns that are well-covered by TUnit's own test suite
• Maintainability: No template-specific code changes required due to good API design

Final Recommendations: ✅ APPROVE

This PR is safe to merge for the following reasons:

1. Clean dependency update: All version references consistently updated across all template projects
2. No breaking changes for templates: Templates use standard APIs unaffected by breaking changes
3. Bug fix included: 0.70.2 contains important fix for double.NaN equality assertions
4. Low migration risk: Breaking changes only affect custom assertion authors (not found in templates)
5. Added value: New migration analyzers will help users transition from other test frameworks
6. Proper testing: This is TUnit's own repository with comprehensive CI/testing

Auto-merge approval: The Renovate Bot configuration with auto-merge is appropriate for this dependency update since it's a clean version bump without compatibility issues for the template projects.

---