chore(deps): update dependency verify to 31.2.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	31.1.0 -> 31.2.0

---

Release Notes

VerifyTests/Verify (Verify)

v31.2.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

---

Code Review Complete ✅

Summary:
This PR updates the Verify dependency from 31.1.0 to 31.2.0, which is a minor version update for the snapshot testing library used in TUnit.

Review Findings:

✅ Code Quality & Best Practices

• Clean change: Single line modification in centralized package management (Directory.Packages.props)
• Follows conventions: Uses TUnit's centralized package version management approach
• Renovate automation: Well-structured automated dependency update

✅ No Bugs or Issues Identified

• Minor version update (31.1.0 → 31.2.0) indicates backward compatibility
• No breaking changes expected based on semantic versioning
• The change is isolated and minimal

⚠️ Potential Version Mismatch

Found related Verify packages that may need updating for consistency:

• Verify.NUnit remains at 31.1.0 (Directory.Packages.props:85)
• Verify.TUnit remains at 31.1.0 (Directory.Packages.props:89)

Recommendation: Consider updating these related packages to 31.2.0 in a follow-up to maintain version consistency.

✅ Performance Considerations

• Verify is used only in test projects for snapshot testing
• No runtime performance impact on production code
• Test execution performance should remain similar or potentially improved

✅ Security Concerns

• Verify is a well-maintained testing library by the established VerifyTests organization
• Minor version updates typically include bug fixes and improvements
• No security concerns identified with this update

✅ Test Coverage

• Verify is used extensively for snapshot testing in:
  • TUnit.Core.SourceGenerator.Tests (source generator output verification)
  • TUnit.Assertions.SourceGenerator.Tests (assertion generator verification)
  • TUnit.PublicAPI (public API surface verification)
• Custom VerifyTUnit wrapper provides TUnit-specific functionality
• Existing snapshot files (.verified.txt) should remain compatible

📋 Usage Analysis

The project uses Verify for critical snapshot testing scenarios:

• Source generator tests: Verifying generated code output matches expectations
• Public API tests: Ensuring API surface remains stable
• Custom implementation: TUnit has its own VerifyTUnit wrapper (TUnit.Core.SourceGenerator.Tests/Verify.cs:194)

Final Assessment:

This is a low-risk, routine dependency update that should be safe to merge. The minor version bump suggests bug fixes and improvements without breaking changes.

Recommendation: ✅ Approve - This update follows best practices and poses minimal risk.

---