chore(deps): update dependency verify to 31.0.5

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	patch	31.0.4 -> 31.0.5

---

Release Notes

VerifyTests/Verify (Verify)

v31.0.5

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 Tasks:

• Examine the dependency change in Directory.Packages.props
• Check Verify usage across the codebase
• Assess risk and compatibility of version 31.0.5
• Provide comprehensive review feedback

---

Review Summary

This PR updates the main Verify package from 31.0.4 → 31.0.5. Overall, this is a low-risk dependency update that should be safe to merge.

Code Quality & Best Practices ✅

• Centralized package management: Correctly uses Directory.Packages.props for version management
• Consistent with project structure: Follows TUnit's dependency management patterns

Findings & Observations

1. Custom Verify Implementation

• TUnit implements its own VerifyTUnit classes in both TUnit.Core.SourceGenerator.Tests/Verify.cs:194 and TUnit.PublicAPI/Verify.cs:167
• These custom implementations provide snapshot testing functionality tailored for TUnit's needs
• The main Verify package is used as a foundation, not directly consumed

2. Package Version Inconsistency ⚠️

• Verify: 31.0.4 → 31.0.5 (this PR)
• Verify.NUnit: Still 31.0.4
• Verify.TUnit: Still 31.0.4

3. Usage Pattern

• Primary usage is in test projects for snapshot verification
• Used in TUnit.Core.SourceGenerator.Tests, TUnit.PublicAPI, and TUnit.Assertions.SourceGenerator.Tests
• Custom implementation handles path normalization, scrubbing, and file comparison

Security & Performance ✅

• No security concerns: Patch version update with no breaking changes
• No performance impact: Internal dependency used only in test scenarios
• Safe update: Verify 31.0.5 is a patch release with bug fixes only

Test Coverage Consideration 📋

According to CLAUDE.md:16-18, snapshot tests should be run and accepted after any source generator changes. Since this is just a dependency update, no snapshot updates should be needed unless the Verify library itself changed verification behavior (unlikely for a patch release).

Recommendation

✅ APPROVE - Safe to merge after CI passes. Consider updating Verify.NUnit and Verify.TUnit to 31.0.5 in a future PR for consistency.

---