chore(deps): update dependency verify.tunit to 30.19.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.TUnit	nuget	patch	30.19.0 -> 30.19.1

---

Release Notes

VerifyTests/Verify (Verify.TUnit)

v30.19.1

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: Dependency Update - Verify.TUnit

Todo List:

• Read the changed file (Directory.Packages.props)
• Analyze the dependency update impact
• Check usage of Verify.TUnit in the codebase
• Review release notes and changelog
• Assess security and compatibility concerns
• Provide comprehensive review feedback

Review Summary ✅

This is a low-risk, automated dependency update that follows good practices.

✅ Code Quality & Best Practices

• Central Package Management: Properly uses Directory.Packages.props for centralized version management
• Clean Update: Single line change from 30.19.0 → 30.19.1 (patch version)
• Consistent Versioning: All Verify packages (Verify, Verify.NUnit, Verify.TUnit) are aligned at 30.19.1

✅ No Issues Found

• No Security Concerns: Patch version updates typically contain bug fixes, not breaking changes
• No Performance Impact: This is a test utility dependency that doesn't affect runtime performance
• No Breaking Changes: Semantic versioning indicates this is a patch release (bug fixes only)

✅ Test Coverage & Usage

The Verify.TUnit package is appropriately used in test projects:

• TUnit.PublicAPI - for API snapshot verification
• TUnit.Core.SourceGenerator.Tests - for source generator output verification
• TUnit.Assertions.SourceGenerator.Tests - for assertion snapshot testing

✅ Repository Compliance

Per CLAUDE.md guidelines, this change:

• Maintains snapshot testing capability (critical for TUnit's architecture)
• Supports both source-generated and reflection modes
• Follows centralized dependency management

📋 Recommendation

APPROVE - This is a safe, routine maintenance update that:

• Follows semantic versioning
• Uses proper dependency management
• Has no security or performance implications
• Maintains test infrastructure compatibility

The automerge configuration is appropriate for this type of patch update.

---