chore(deps): update dependency verify to 30.19.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	patch	30.19.1 -> 30.19.2

---

Release Notes

VerifyTests/Verify (Verify)

v30.19.2

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 for Verify Dependency Update

Todo List

• Read and understand the changed file (Directory.Packages.props)
• Review CLAUDE.md for testing requirements
• Analyze the Verify package usage in the codebase
• Check release notes for potential breaking changes
• Assess security and compatibility implications
• Provide comprehensive review feedback

---

🔍 Review Summary

This is a patch version update for the Verify package from 30.19.1 to 30.19.2 - a low-risk dependency bump.

✅ Positive Aspects

1. Safe Change: Patch version updates typically contain only bug fixes with no breaking changes
2. Centralized Management: Using Directory.Packages.props for central package management is excellent practice
3. Automated Process: Renovate bot automation ensures dependencies stay current
4. Extensive Usage: Verify is heavily used for snapshot testing throughout TUnit's test suite

⚠️ Issues Found

Critical: Version Inconsistency

The main Verify package is updated to 30.19.2, but related packages remain on 30.19.1:

Directory.Packages.props:

• Line 85: Verify → 30.19.2 ✅ (updated)
• Line 86: Verify.NUnit → 30.19.1 ⚠️ (outdated)
• Line 90: Verify.TUnit → 30.19.1 ⚠️ (outdated)

Recommendation: Update all Verify-related packages to the same version for consistency and to avoid potential compatibility issues.

🔧 Technical Assessment

Impact Analysis

• Scope: Testing infrastructure only (not production code)
• Risk Level: Low (patch version, test-only dependency)
• Compatibility: Should maintain full backward compatibility

Usage Context

Verify is extensively used for:

• Source generator snapshot testing (TUnit.Core.SourceGenerator.Tests)
• Public API verification (TUnit.PublicAPI tests per CLAUDE.md)
• General test verification across the codebase

Testing Requirements (per CLAUDE.md)

Before merging, you should run:

# Source generator snapshots
dotnet test TUnit.Core.SourceGenerator.Tests

# Public API snapshots  
dotnet test TUnit.PublicAPI

# Full test suite
dotnet test

🛡️ Security & Performance

• Security: No concerns for a testing dependency patch update
• Performance: No performance impact expected from a patch release
• Dependencies: No new transitive dependencies introduced

📋 Recommendations

1. Immediate: Consider updating Verify.NUnit and Verify.TUnit to 30.19.2 for consistency
2. Testing: Run the snapshot tests mentioned above to ensure no regressions
3. Automation: This PR can be safely auto-merged after tests pass

✅ Code Quality

The change itself is minimal and follows proper package management practices. No code quality concerns.

---

Overall Assessment: ✅ APPROVE - Safe dependency update with minor version inconsistency to address.