chore(deps): update dependency verify to 30.6.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	30.5.0 -> 30.6.0

---

Release Notes

VerifyTests/Verify (Verify)

v30.6.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: Dependency Update - Verify 30.5.0 → 30.6.0

Review Checklist:

• Analyze the changed file (Directory.Packages.props)
• Review code quality and best practices
• Check for potential bugs or issues
• Assess performance considerations
• Evaluate security concerns
• Review test coverage implications
• Provide final review feedback

Review Summary

This PR updates the Verify package from version 30.5.0 to 30.6.0. After analyzing the codebase, here are my findings:

✅ Code Quality & Best Practices

• Clean dependency management: Uses centralized package management via Directory.Packages.props
• Proper usage pattern: The project implements its own verification framework (VerifyTUnit) that appears to be inspired by but independent of the external Verify package
• Good separation: External Verify package is only used in test projects (TUnit.PublicAPI and TUnit.Core.SourceGenerator.Tests)

⚠️ Potential Issues Found

1. Version Mismatch: Line 86 shows Verify.NUnit is still on version 30.5.0 while Verify is being updated to 30.6.0. This could cause compatibility issues.

   • Recommendation: Update Verify.NUnit to 30.6.0 as well to maintain version consistency

2. Custom Implementation Risk: The codebase has its own VerifyTUnit implementations that duplicate functionality from the external Verify package. This could lead to:

   • Maintenance overhead
   • Feature gaps compared to the official library
   • Potential bugs in custom implementations

🔒 Security Considerations

• Low Risk: Minor version update (30.5.0 → 30.6.0) with no apparent security implications
• Package Source: Verify is a well-established testing library from VerifyTests organization
• No Breaking Changes: Version indicates backward compatibility

⚡ Performance Considerations

• Minimal Impact: Test-only dependency, no runtime performance effects
• File I/O: Custom verify implementations use file operations that could be optimized by using the official library's features

🧪 Test Coverage

• No Impact: This is a testing utility dependency, not affecting production code
• Usage: Only used in TUnit.PublicAPI and TUnit.Core.SourceGenerator.Tests projects for snapshot testing

📋 Recommendations

1. Immediate: Update Verify.NUnit from 30.5.0 to 30.6.0 to match the main Verify package
2. Future Consideration: Evaluate whether to use the official Verify library instead of custom VerifyTUnit implementations to reduce maintenance burden and leverage official features/fixes

✅ Approval Status

This dependency update is safe to merge once the version mismatch issue is addressed. The minor version bump suggests bug fixes and improvements without breaking changes.