chore(deps): update dependency verify to 30.20.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	30.19.2 -> 30.20.0

---

Release Notes

VerifyTests/Verify (Verify)

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

Todo List:

• Examine the changed file (Directory.Packages.props)
• Understand the Verify package usage in the codebase
• Assess the version change impact
• Check for any potential breaking changes
• Provide comprehensive review feedback

Review Summary

This PR updates the Verify package from 30.19.2 to 30.20.0, which is a minor version update with low risk.

✅ Code Quality & Best Practices

• Centralized package management: The change correctly uses Directory.Packages.props for centralized version management, which is a best practice
• Consistent approach: The change follows the established pattern for dependency updates in this codebase

⚠️ Potential Issues Identified

1. Version Mismatch: I notice that related Verify packages are not updated in sync:

   • Verify → 30.20.0 (updated)
   • Verify.NUnit → 30.19.2 (not updated)
   • Verify.TUnit → 30.19.2 (not updated)

2. Custom Implementation: TUnit implements its own snapshot testing via custom VerifySettingsTask classes in:

   • TUnit.PublicAPI/Verify.cs:9-171
   • TUnit.Core.SourceGenerator.Tests/Verify.cs:9-198

🔒 Security Considerations

• Low risk: This is a legitimate package update from the well-known VerifyTests project
• Minor version: Semantic versioning suggests this should only contain backward-compatible additions

⚡ Performance Considerations

• Minimal impact: Since TUnit uses custom verification implementations rather than the Verify package directly, performance impact should be negligible
• Snapshot testing: The main usage is for snapshot/approval testing which only runs during test execution

🧪 Test Coverage

• Good coverage: The codebase has extensive snapshot tests that will validate the dependency update
• Custom verification: TUnit's custom verification logic in Verify.cs files reduces dependency on the external package

📋 Recommendations

1. Consider updating related packages: To maintain consistency, consider updating Verify.NUnit and Verify.TUnit to matching versions in a follow-up PR
2. Run snapshot tests: Ensure all snapshot tests pass after this update (as mentioned in CLAUDE.md)
3. Monitor for issues: Since this is a minor update, it should be safe, but monitor for any unexpected behavior

✅ Approval

This dependency update is safe to merge. The version change is minor, the risk is low, and TUnit's custom verification implementations provide isolation from potential breaking changes in the external package.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Dependency Update

Todo List:

• Examine the changed file (Directory.Packages.props)
• Understand the Verify package usage in the codebase
• Assess the version change impact
• Check for any potential breaking changes
• Provide comprehensive review feedback

Review Summary

This PR updates the Verify package from 30.19.2 to 30.20.0, which is a minor version update with low risk.

✅ Code Quality & Best Practices

• Centralized package management: The change correctly uses Directory.Packages.props for centralized version management, which is a best practice
• Consistent approach: The change follows the established pattern for dependency updates in this codebase

⚠️ Potential Issues Identified

1. Version Mismatch: I notice that related Verify packages are not updated in sync:

   • Verify → 30.20.0 (updated)
   • Verify.NUnit → 30.19.2 (not updated)
   • Verify.TUnit → 30.19.2 (not updated)

2. Custom Implementation: TUnit implements its own snapshot testing via custom VerifySettingsTask classes in:

   • TUnit.PublicAPI/Verify.cs:9-171
   • TUnit.Core.SourceGenerator.Tests/Verify.cs:9-198

🔒 Security Considerations

• Low risk: This is a legitimate package update from the well-known VerifyTests project
• Minor version: Semantic versioning suggests this should only contain backward-compatible additions

⚡ Performance Considerations

• Minimal impact: Since TUnit uses custom verification implementations rather than the Verify package directly, performance impact should be negligible
• Snapshot testing: The main usage is for snapshot/approval testing which only runs during test execution

🧪 Test Coverage

• Good coverage: The codebase has extensive snapshot tests that will validate the dependency update
• Custom verification: TUnit's custom verification logic in Verify.cs files reduces dependency on the external package

📋 Recommendations

1. Consider updating related packages: To maintain consistency, consider updating Verify.NUnit and Verify.TUnit to matching versions in a follow-up PR
2. Run snapshot tests: Ensure all snapshot tests pass after this update (as mentioned in CLAUDE.md)
3. Monitor for issues: Since this is a minor update, it should be safe, but monitor for any unexpected behavior

✅ Approval

This dependency update is safe to merge. The version change is minor, the risk is low, and TUnit's custom verification implementations provide isolation from potential breaking changes in the external package.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Dependency Update

Todo List:

• Examine the changed file (Directory.Packages.props)
• Understand the Verify package usage in the codebase
• Assess the version change impact
• Check for any potential breaking changes
• Provide comprehensive review feedback

Review Summary

This PR updates the Verify package from 30.19.2 to 30.20.0, which is a minor version update with low risk.

✅ Code Quality & Best Practices

• Centralized package management: The change correctly uses Directory.Packages.props for centralized version management, which is a best practice
• Consistent approach: The change follows the established pattern for dependency updates in this codebase
• Version alignment: I notice that ALL related Verify packages are updated in sync:
  • Verify → 30.20.0 (updated)
  • Verify.NUnit → 30.20.0 (updated)
  • Verify.TUnit → 30.20.0 (updated)

✅ Custom Implementation Analysis

TUnit implements its own snapshot testing via custom VerifySettingsTask classes in:

• TUnit.PublicAPI/Verify.cs:9-171
• TUnit.Core.SourceGenerator.Tests/Verify.cs:9-198

This custom implementation provides isolation from external package changes, which reduces risk significantly.

🔒 Security Considerations

• Low risk: This is a legitimate package update from the well-known VerifyTests project
• Minor version: Semantic versioning suggests this should only contain backward-compatible additions
• Trusted source: The Verify library is widely used and maintained by the VerifyTests organization

⚡ Performance Considerations

• Minimal impact: Since TUnit uses custom verification implementations rather than the external Verify package directly, performance impact should be negligible
• Snapshot testing only: The main usage is for snapshot/approval testing which only runs during test execution, not in production code

🧪 Test Coverage

• Good coverage: The codebase has extensive snapshot tests that will validate the dependency update
• Custom verification: TUnit's custom verification logic in Verify.cs files reduces dependency on the external package
• Limited external usage: Only found minimal direct usage of VerifyTests in GlobalUsings.cs

🔍 Breaking Changes Assessment

• Version jump: 30.19.2 → 30.20.0 is a standard minor version increment
• Semantic versioning: Should only contain new features and bug fixes, no breaking changes
• Risk mitigation: TUnit's custom implementation acts as a buffer against potential breaking changes

✅ Approval

This dependency update is safe to merge. The version change is minor, all related packages are updated consistently, the risk is low, and TUnit's custom verification implementations provide excellent isolation from potential issues in the external package.

📋 Recommendations

1. No immediate action required: The update appears safe and well-coordinated
2. Monitor CI: Ensure all tests continue to pass after this update
3. Follow CLAUDE.md guidance: Run snapshot tests if any source generator or public API changes are detected

---