chore(deps): update verify to 31.7.3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	patch	31.7.2 -> 31.7.3
Verify.NUnit	nuget	patch	31.7.2 -> 31.7.3
Verify.TUnit	nuget	patch	31.7.2 -> 31.7.3

---

Release Notes

VerifyTests/Verify (Verify)

v31.7.3

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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 these updates 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 Package Updates

Todo List:

• Review Directory.Packages.props changes
• Analyze impact of Verify package updates
• Check for potential compatibility issues
• Assess test coverage implications
• Provide security and performance feedback
• Make recommendations

Review Summary

This is a clean and safe dependency update PR that bumps three Verify-related packages from 31.7.2 to 31.7.3 (patch version).

Code Quality ✅

Changes Made:

• Directory.Packages.props:84: Verify 31.7.2 → 31.7.3
• Directory.Packages.props:85: Verify.NUnit 31.7.2 → 31.7.3
• Directory.Packages.props:89: Verify.TUnit 31.7.2 → 31.7.3

The changes follow proper central package management patterns using Directory.Packages.props.

Potential Issues ✅

No Breaking Changes Expected:

• Patch version updates (x.x.3) typically contain only bug fixes
• Release notes indicate minimal changes with no breaking changes listed
• Verify packages maintain strong backward compatibility

Performance Considerations ✅

Low Impact:

• Verify is primarily used in test projects, not production runtime
• Usage is confined to test/snapshot verification scenarios
• No performance-critical code paths affected

Security Concerns ✅

Low Risk:

• Patch updates often include security fixes
• Verify packages are well-maintained with good security practices
• Used only in test context, not production deployments

Test Coverage ✅

Comprehensive Usage Found:

• TUnit.Core.SourceGenerator.Tests - Uses Verify.TUnit for snapshot testing
• TUnit.PublicAPI - Uses Verify.TUnit for API change detection
• TUnit.Assertions.SourceGenerator.Tests - Uses Verify.TUnit for generated code testing
• Critical test infrastructure depends on these packages

Impact Analysis:

• Core snapshot testing functionality depends on Verify packages
• Public API change detection relies on Verify.TUnit
• Source generator output verification uses these packages

Recommendations ✅

1. Approve and Merge: This is a safe patch update with minimal risk
2. CI Validation: Ensure all tests pass, especially:
   • Source generator snapshot tests
   • Public API verification tests
   • Any analyzer/assertion tests using Verify
3. No Manual Testing Required: Patch updates with comprehensive test coverage
4. Monitor: Watch for any test failures in CI that might indicate compatibility issues

Risk Assessment: LOW ✅

• Patch version update
• Well-tested packages
• Non-production dependencies
• Comprehensive test coverage exists
• No breaking changes expected

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Package Updates

Todo List:

• Review Directory.Packages.props changes
• Analyze impact of Verify package updates
• Check for potential compatibility issues
• Assess test coverage implications
• Provide security and performance feedback
• Make recommendations

Review Summary

This is a clean and safe dependency update PR that bumps three Verify-related packages from 31.7.2 to 31.7.3 (patch version).

Code Quality ✅

Changes Made:

• Directory.Packages.props:84: Verify 31.7.2 → 31.7.3
• Directory.Packages.props:85: Verify.NUnit 31.7.2 → 31.7.3
• Directory.Packages.props:89: Verify.TUnit 31.7.2 → 31.7.3

The changes follow proper central package management patterns using Directory.Packages.props.

Potential Issues ✅

No Breaking Changes Expected:

• Patch version updates (x.x.3) typically contain only bug fixes
• Release notes indicate minimal changes with no breaking changes listed
• Verify packages maintain strong backward compatibility

Performance Considerations ✅

Low Impact:

• Verify is primarily used in test projects, not production runtime
• Usage is confined to test/snapshot verification scenarios
• No performance-critical code paths affected

Security Concerns ✅

Low Risk:

• Patch updates often include security fixes
• Verify packages are well-maintained with good security practices
• Used only in test context, not production deployments

Test Coverage ✅

Comprehensive Usage Found:

• TUnit.Core.SourceGenerator.Tests - Uses Verify.TUnit for snapshot testing
• TUnit.PublicAPI - Uses Verify.TUnit for API change detection
• TUnit.Assertions.SourceGenerator.Tests - Uses Verify.TUnit for generated code testing
• 342 verified snapshot files depend on these packages

Impact Analysis:

• Core snapshot testing functionality depends on Verify packages
• Public API change detection relies on Verify.TUnit
• Source generator output verification uses these packages

Recommendations ✅

1. Approve and Merge: This is a safe patch update with minimal risk
2. CI Validation: Ensure all tests pass, especially:
   • Source generator snapshot tests
   • Public API verification tests
   • Any analyzer/assertion tests using Verify
3. No Manual Testing Required: Patch updates with comprehensive test coverage
4. Monitor: Watch for any test failures in CI that might indicate compatibility issues

Risk Assessment: LOW ✅

• Patch version update
• Well-tested packages
• Non-production dependencies
• Comprehensive test coverage exists
• No breaking changes expected

---

[claude]

Claude Code is working…

I'll analyze this and get back to you.

View job run

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Package Updates

Todo List:

• Review Directory.Packages.props changes
• Analyze impact of Verify package updates
• Check for potential compatibility issues
• Assess test coverage implications
• Provide security and performance feedback
• Make recommendations

Review Summary

This is a clean and safe dependency update PR that bumps three Verify-related packages from 31.7.2 to 31.7.3 (patch version).

Code Quality ✅

Changes Made:

• Directory.Packages.props:84: Verify 31.7.2 → 31.7.3
• Directory.Packages.props:85: Verify.NUnit 31.7.2 → 31.7.3
• Directory.Packages.props:89: Verify.TUnit 31.7.2 → 31.7.3

The changes follow proper central package management patterns using Directory.Packages.props.

Potential Issues ✅

No Breaking Changes Expected:

• Patch version updates (x.x.3) typically contain only bug fixes
• Release notes indicate minimal changes with no breaking changes listed
• Verify packages maintain strong backward compatibility

Performance Considerations ✅

Low Impact:

• Verify is primarily used in test projects, not production runtime
• Usage is confined to test/snapshot verification scenarios
• No performance-critical code paths affected

Security Concerns ✅

Low Risk:

• Patch updates often include security fixes
• Verify packages are well-maintained with good security practices
• Used only in test context, not production deployments

Test Coverage ✅

Comprehensive Usage Found:

• TUnit.Core.SourceGenerator.Tests - Uses Verify.TUnit for snapshot testing
• TUnit.PublicAPI - Uses Verify.TUnit for API change detection
• TUnit.Assertions.SourceGenerator.Tests - Uses Verify.TUnit for generated code testing
• 342 verified snapshot files depend on these packages

Impact Analysis:

• Core snapshot testing functionality depends on Verify packages
• Public API change detection relies on Verify.TUnit
• Source generator output verification uses these packages

Recommendations ✅

1. Approve and Merge: This is a safe patch update with minimal risk
2. CI Validation: Ensure all tests pass, especially:
   • Source generator snapshot tests
   • Public API verification tests
   • Any analyzer/assertion tests using Verify
3. No Manual Testing Required: Patch updates with comprehensive test coverage
4. Monitor: Watch for any test failures in CI that might indicate compatibility issues

Risk Assessment: LOW ✅

• Patch version update
• Well-tested packages
• Non-production dependencies
• Comprehensive test coverage exists
• No breaking changes expected

---