chore(deps): update dependency verify to 30.15.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	30.14.0 -> 30.15.0

---

Release Notes

VerifyTests/Verify (Verify)

v30.15.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:

• Read the changed file to understand the update
• Analyze the repository structure to understand Verify usage
• Check for any potential breaking changes or issues
• Provide comprehensive review feedback

Review Summary

This PR updates the Verify package from 30.14.0 to 30.15.0 - a minor version update that appears safe and follows the project's regular dependency update pattern.

✅ Code Quality & Best Practices

• Centralized package management: Uses Directory.Packages.props for version management ✓
• Consistent versioning: Follows semantic versioning with minor update ✓
• Automated updates: Renovate bot ensures timely dependency maintenance ✓

✅ Potential Issues Assessment

• Breaking changes: None expected - This is a minor version update (30.14.0 → 30.15.0)
• Version alignment: Potential consideration - Verify.TUnit is at 30.13.0 while base Verify is updating to 30.15.0. This version skew is typically acceptable for Verify packages
• Update frequency: Recent commits show regular Verify updates (30.13.0 → 30.14.0 → 30.15.0), indicating active maintenance

✅ Performance Considerations

• Impact: Minimal - Verify is a testing-only dependency used for snapshot testing
• Runtime: No production runtime impact as it's test-only
• Build time: Potential minor improvements or bug fixes in snapshot comparison logic

✅ Security Concerns

• Risk level: Very Low - Testing framework dependency with no production exposure
• Source: Verify is a well-maintained OSS project by VerifyTests organization
• Scope: Limited to test execution environment only

✅ Test Coverage

• Existing coverage: Extensive usage across multiple test projects:
  • TUnit.Core.SourceGenerator.Tests
  • TUnit.PublicAPI
  • TUnit.Assertions.SourceGenerator.Tests
• Custom implementation: Project has custom VerifyTUnit wrapper in /TUnit.Core.SourceGenerator.Tests/Verify.cs:194-197
• Snapshot tests: Critical for source generator validation - will catch any compatibility issues

📋 Recommendations

1. Proceed with merge - This is a standard, low-risk dependency update
2. Monitor CI/CD - Existing snapshot tests will validate compatibility
3. Future consideration - May want to update Verify.TUnit from 30.13.0 to align versions in a future update

🔧 Notes for CLAUDE.md Compliance

• Follows project's rule to run snapshot tests when changing dependencies: dotnet test TUnit.Core.SourceGenerator.Tests
• Aligns with performance focus - testing improvements don't impact runtime performance
• Maintains behavioral parity between execution modes through comprehensive test coverage

Overall Assessment: ✅ APPROVED - Safe, routine dependency update with minimal risk and proper safeguards in place.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Dependency Update

Todo List:

• Read the changed file to understand the update
• Analyze the repository structure to understand Verify usage
• Check for any potential breaking changes or issues
• Provide comprehensive review feedback

Review Summary

This PR updates the Verify package from 30.14.0 to 30.15.0 - a minor version update that appears safe and follows the project's regular dependency update pattern.

✅ Code Quality & Best Practices

• Centralized package management: Uses Directory.Packages.props for version management ✓
• Consistent versioning: Follows semantic versioning with minor update ✓
• Automated updates: Renovate bot ensures timely dependency maintenance ✓

✅ Potential Issues Assessment

• Breaking changes: None expected - This is a minor version update (30.14.0 → 30.15.0)
• Version alignment: Potential consideration - Verify.TUnit is at 30.13.0 while base Verify is updating to 30.15.0. This version skew is typically acceptable for Verify packages
• Update frequency: Recent commits show regular Verify updates (30.13.0 → 30.14.0 → 30.15.0), indicating active maintenance

✅ Performance Considerations

• Impact: Minimal - Verify is a testing-only dependency used for snapshot testing
• Runtime: No production runtime impact as it's test-only
• Build time: Potential minor improvements or bug fixes in snapshot comparison logic

✅ Security Concerns

• Risk level: Very Low - Testing framework dependency with no production exposure
• Source: Verify is a well-maintained OSS project by VerifyTests organization
• Scope: Limited to test execution environment only

✅ Test Coverage

• Existing coverage: Extensive usage across multiple test projects:
  • TUnit.Core.SourceGenerator.Tests
  • TUnit.PublicAPI
  • TUnit.Assertions.SourceGenerator.Tests
• Custom implementation: Project has custom VerifyTUnit wrapper in /TUnit.Core.SourceGenerator.Tests/Verify.cs:194-197
• Snapshot tests: Critical for source generator validation - will catch any compatibility issues

📋 Recommendations

1. Proceed with merge - This is a standard, low-risk dependency update
2. Monitor CI/CD - Existing snapshot tests will validate compatibility
3. Future consideration - May want to update Verify.TUnit from 30.13.0 to align versions in a future update

🔧 Notes for CLAUDE.md Compliance

• Follows project's rule to run snapshot tests when changing dependencies: dotnet test TUnit.Core.SourceGenerator.Tests
• Aligns with performance focus - testing improvements don't impact runtime performance
• Maintains behavioral parity between execution modes through comprehensive test coverage

Overall Assessment: ✅ APPROVED - Safe, routine dependency update with minimal risk and proper safeguards in place.

---