chore(deps): update dependency verify to 30.11.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	30.10.0 -> 30.11.0

---

Release Notes

VerifyTests/Verify (Verify)

v30.11.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.11.0

Todo List:

• Examine the changed file (Directory.Packages.props)
• Understand how Verify package is used in the codebase
• Check for any potential compatibility issues
• Review release notes and changes
• Provide comprehensive feedback on the update

---

🔍 Analysis Summary

Change: Updates Verify package from 30.10.0 → 30.11.0 in Directory.Packages.props:85

⚠️ Issues Identified

1. Version Mismatch (Critical)

   • Verify.NUnit remains at 30.10.0 (line 86) while Verify is updated to 30.11.0
   • Recommendation: Update Verify.NUnit to 30.11.0 to maintain package consistency

2. Potentially Unused Dependency

   • The codebase implements custom snapshot verification systems (VerifyTUnit, VerifySettingsTask)
   • No direct usage of the official VerifyTests library found
   • Question: Is the Verify package actually needed, or can it be removed?

✅ Positive Aspects

• Low Risk: Since TUnit uses custom verification implementations, this update has minimal impact
• Minor Version: 30.10.0 → 30.11.0 is a minor version bump, typically backward compatible
• Clean Change: Single line modification in centralized package management

🔧 Recommendations

1. Fix Version Mismatch:

   - <PackageVersion Include="Verify.NUnit" Version="30.10.0" />
   + <PackageVersion Include="Verify.NUnit" Version="30.11.0" />

2. Verify Necessity: Consider if the Verify package is still needed given TUnit's custom implementations

3. Test Coverage: The change appears safe, but run snapshot tests to ensure compatibility:

   dotnet test TUnit.Core.SourceGenerator.Tests
   dotnet test TUnit.PublicAPI

🛡️ Security & Performance

• Security: ✅ No security concerns for this minor version update
• Performance: ✅ No performance impact expected
• Breaking Changes: ✅ None expected for minor version bump

📋 Overall Assessment

Approve with Fix Required - The update itself is safe, but the version mismatch with Verify.NUnit should be addressed before merging.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Dependency Update - Verify 30.11.0

Todo List:

• Examine the changed file (Directory.Packages.props)
• Search for Verify package usage in the codebase
• Check for related package version consistency
• Review release notes and changes between versions
• Assess security and performance implications
• Provide comprehensive feedback on the update

---

🔍 Analysis Summary

Change: Updates Verify package from 30.10.0 → 30.11.0 in Directory.Packages.props:85
Related: Verify.NUnit is also at 30.11.0 (consistent versioning)

✅ Positive Aspects

1. Version Consistency: Both Verify and Verify.NUnit are properly aligned at 30.11.0
2. Low Impact: TUnit uses custom snapshot verification implementations (VerifyTUnit, VerifySettingsTask)
3. Minor Version: 30.10.0 → 30.11.0 is a minor version bump, typically backward compatible
4. Clean Change: Single line modification in centralized package management

🔧 Package Usage Analysis

The VerifyTests package is referenced in two test projects:

• TUnit.Core.SourceGenerator.Tests.csproj:23
• TUnit.PublicAPI.csproj

However, TUnit implements its own verification system:

• Custom VerifyTUnit class with Verify() method in TUnit.Core.SourceGenerator.Tests/Verify.cs:194
• Custom VerifySettingsTask for snapshot verification in the same file
• The codebase uses await Verify(...) calls that resolve to TUnit's custom implementation, not the official VerifyTests library

💡 Recommendations

1. Consider Removal: Since TUnit has comprehensive custom verification implementations, evaluate if the Verify package is still necessary
2. Documentation: If keeping the package, document why both custom and official verification coexist
3. No Breaking Changes Expected: This minor version update should not affect the existing codebase

🛡️ Security & Performance Assessment

• Security: ✅ No security concerns for this minor version update
• Performance: ✅ No performance impact expected since TUnit uses custom implementations
• Compatibility: ✅ Minor version bump maintains backward compatibility
• Breaking Changes: ✅ None expected for 30.x series

🧪 Test Coverage Considerations

The change affects test dependencies only. Run snapshot tests to ensure compatibility:

dotnet test TUnit.Core.SourceGenerator.Tests
dotnet test TUnit.PublicAPI

📋 Overall Assessment

✅ APPROVE - This is a safe, low-risk dependency update. The version consistency between Verify and Verify.NUnit is properly maintained, and TUnit's custom verification systems insulate it from potential issues in the official VerifyTests library.

The update follows semantic versioning best practices and maintains package alignment across the solution.

---