chore(deps): update dependency verify to 30.13.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	30.12.0 -> 30.13.0

---

Release Notes

VerifyTests/Verify (Verify)

v30.13.0

Compare Source

---

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 this update 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: Verify Dependency Update

Review Summary ✅ APPROVED

This is a low-risk minor version update of the Verify package from 30.11.0 to 30.12.0.

Key Findings:

✅ Code Quality & Architecture

• The project uses custom snapshot testing implementations (VerifyTUnit classes) rather than the official Verify APIs
• Both TUnit.Core.SourceGenerator.Tests and TUnit.PublicAPI have their own Verify implementations with robust features:
  • File path scrubbing for cross-platform compatibility
  • Line-by-line content scrubbing
  • Platform-specific test naming (UniqueForTargetFrameworkAndVersion)
  • Proper error handling for missing verification files

✅ Security Assessment

• No security concerns - the Verify package is only used as a project dependency reference
• No actual usage of Verify APIs in the codebase (searched for VerifyTests namespace usage)

✅ Performance Considerations

• Minimal performance impact expected from this minor version update
• Custom implementations handle the actual snapshot testing logic

✅ Compatibility

• Minor version update (30.11.0 → 30.12.0) with no breaking changes expected
• Change follows semantic versioning principles

Minor Inconsistency Noted:

• Line 86: Verify.NUnit package remains at 30.11.0 (not updated with main Verify package)
• However, Verify.NUnit appears unused (no project references found), so this inconsistency has no functional impact

Recommendations:

1. ✅ Safe to merge - This is a routine dependency maintenance update
2. 📋 Consider updating Verify.NUnit to 30.12.0 for consistency in a future cleanup PR
3. 🧪 The existing test suite should verify the custom Verify implementations continue working correctly

Test Coverage Impact:

No test coverage changes needed - the custom VerifyTUnit implementations handle all snapshot testing functionality independently of the official Verify package APIs.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Dependency Update

Review Summary ✅ APPROVED

This is a low-risk minor version update of the Verify package from 30.11.0 to 30.12.0.

Todo List:

• Read the changed Directory.Packages.props file
• Analyze codebase usage of Verify package
• Check for potential compatibility issues
• Review security and performance implications
• Provide comprehensive review feedback

Key Findings:

✅ Code Quality & Architecture

• The project uses custom snapshot testing implementations (VerifyTUnit classes) rather than the official Verify APIs
• Both TUnit.Core.SourceGenerator.Tests and TUnit.PublicAPI have their own Verify implementations with robust features:
  • File path scrubbing for cross-platform compatibility (lines 64-82 in both files)
  • Line-by-line content scrubbing capabilities
  • Platform-specific test naming (UniqueForTargetFrameworkAndVersion)
  • Proper error handling for missing verification files
  • Normalized line ending handling for cross-platform consistency

✅ Security Assessment

• No security concerns identified - the Verify package is only used as a project dependency reference
• No actual usage of Verify APIs found in the codebase (searched for VerifyTests namespace usage)
• The custom implementations handle all verification logic independently

✅ Performance Considerations

• Minimal performance impact expected from this minor version update
• Custom implementations handle the actual snapshot testing logic, so core functionality remains unchanged
• No breaking changes expected in a minor version update

✅ Compatibility

• Minor version update (30.11.0 → 30.12.0) follows semantic versioning principles
• Both Verify and Verify.NUnit are updated to the same version (30.12.0) maintaining consistency
• No API changes affect the codebase since only package references are used, not the actual APIs

✅ Test Coverage Impact

• No test coverage changes needed - the custom VerifyTUnit implementations in /home/runner/work/TUnit/TUnit/TUnit.Core.SourceGenerator.Tests/Verify.cs:194 and /home/runner/work/TUnit/TUnit/TUnit.PublicAPI/Verify.cs:167 handle all snapshot testing functionality independently

Change Analysis:

The only change is updating line 85 in Directory.Packages.props:

- <PackageVersion Include="Verify" Version="30.11.0" />
+ <PackageVersion Include="Verify" Version="30.12.0" />

Recommendations:

1. ✅ Safe to merge - This is a routine dependency maintenance update
2. 🧪 The existing test suite will verify the custom Verify implementations continue working correctly
3. 📋 Consider running the snapshot tests to ensure no unexpected changes: dotnet test TUnit.Core.SourceGenerator.Tests and dotnet test TUnit.PublicAPI

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Dependency Update ✅ APPROVED

Review Summary

This is a low-risk minor version update of the Verify package from 30.11.0 to 30.12.0.

Todo List:

• Read the changed Directory.Packages.props file
• Analyze codebase usage of Verify package
• Check for potential compatibility issues
• Review security and performance implications
• Provide comprehensive review feedback

---

Key Findings:

✅ Code Quality & Architecture

The project uses custom snapshot testing implementations (VerifyTUnit classes) rather than the official Verify APIs:

• Both TUnit.Core.SourceGenerator.Tests/Verify.cs:194 and TUnit.PublicAPI/Verify.cs:167 contain robust custom implementations
• Features include:
  • File path scrubbing for cross-platform compatibility (lines 67-76 in both files)
  • Line-by-line content scrubbing capabilities
  • Platform-specific test naming (UniqueForTargetFrameworkAndVersion)
  • Proper error handling for missing verification files
  • Normalized line ending handling for cross-platform consistency

✅ Security Assessment

• No security concerns identified - the Verify package is only used as a project dependency reference
• No actual usage of Verify APIs found in the codebase (searched for VerifyTests namespace usage)
• Custom implementations handle all verification logic independently

✅ Performance Considerations

• Minimal performance impact expected from this minor version update
• Custom implementations handle the actual snapshot testing logic, so core functionality remains unchanged
• No breaking changes expected in a minor version update following semantic versioning

✅ Compatibility

• Minor version update (30.11.0 → 30.12.0) follows semantic versioning principles
• Both Verify and Verify.NUnit updated to the same version (30.12.0) maintaining consistency
• No API changes affect the codebase since only package references are used, not the actual APIs

✅ Test Coverage Impact

No test coverage changes needed - the custom VerifyTUnit implementations handle all snapshot testing functionality independently of the official Verify package APIs.

---

Change Analysis:

The only changes are in Directory.Packages.props:

- <PackageVersion Include="Verify" Version="30.11.0" />
+ <PackageVersion Include="Verify" Version="30.12.0" />

Recommendations:

1. ✅ Safe to merge - This is a routine dependency maintenance update
2. 🧪 Consider running the snapshot tests to ensure no unexpected changes: dotnet test TUnit.Core.SourceGenerator.Tests and dotnet test TUnit.PublicAPI
3. 📋 The existing test suite will verify the custom Verify implementations continue working correctly

---