Skip to content

Conversation

@thomhurst
Copy link
Owner

@thomhurst thomhurst commented Oct 13, 2025

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
👒 Dependencies

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

v0.71.4: 0.71.4

What's Changed

🏕 Changes
👒 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
👒 Dependencies

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

v0.70.7: 0.70.7

What's Changed

🏕 Changes
👒 Dependencies

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

v0.70.4: 0.70.4

What's Changed

🏕 Changes
👒 Dependencies

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

v0.70.2: 0.70.2

What's Changed
🏕 Changes
👒 Dependencies

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 🛠
🏕 Changes
👒 Dependencies

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.

@thomhurst thomhurst added dependencies Pull requests that update a dependency file MINOR renovate-bot labels Oct 13, 2025
@thomhurst thomhurst enabled auto-merge (squash) October 13, 2025 15:45
@claude
Copy link
Contributor

claude bot commented Oct 13, 2025

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
Copy link
Contributor

claude bot commented Oct 13, 2025

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
Copy link
Contributor

claude bot commented Oct 13, 2025

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.


@thomhurst thomhurst changed the title chore(deps): update tunit to 0.70.0 chore(deps): update tunit to 0.70.2 Oct 13, 2025
@claude
Copy link
Contributor

claude bot commented Oct 13, 2025

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
Copy link
Contributor

claude bot commented Oct 14, 2025

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.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file MINOR renovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants