chore(deps): update dependency verify to 31.0.3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	patch	31.0.2 -> 31.0.3

---

Release Notes

VerifyTests/Verify (Verify)

v31.0.3

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

---

Reviewing PR: Update dependency verify to 31.0.3

Todo List:

• Read the changed file (Directory.Packages.props)
• Analyze the dependency update scope and impact
• Check Verify library usage in the codebase
• Review for potential compatibility issues
• Provide comprehensive review feedback

---

Review Feedback

This is a clean, low-risk dependency update that follows good practices. Here's my analysis:

✅ Code Quality & Best Practices

• Proper use of centralized package management via Directory.Packages.props
• Clean patch version update (31.0.2 → 31.0.3) minimizes breaking change risk
• Automated dependency management via Renovate Bot ensures consistency

✅ Potential Issues Assessment

• No breaking changes expected: Patch versions in semantic versioning maintain backward compatibility
• Consistent pattern: Recent commits show similar dependency updates processed safely
• Isolated change: Only the core Verify package version is updated

⚠️ Version Alignment Consideration

I noticed a potential inconsistency in your dependency versions:

Verify         31.0.3  ← Updated in this PR
Verify.NUnit   31.0.2  ← Still on older version  
Verify.TUnit   31.0.2  ← Still on older version

Recommendation: Consider updating Verify.NUnit and Verify.TUnit to 31.0.3 as well to maintain version alignment, though this isn't critical for functionality.

✅ Performance & Security

• Patch updates typically include bug fixes and minor performance improvements
• No security concerns with this update
• Verify library is extensively used for snapshot testing across the codebase

✅ Test Coverage

• TUnit's comprehensive test suite should catch any compatibility issues
• Verify is primarily used in test projects, reducing production risk
• The project follows good practices with snapshot testing validation

Overall Assessment

✅ APPROVED - This is a safe, well-managed dependency update that should be merged.

---

[claude]

Claude finished @thomhurst's task —— View job

---

Reviewing PR: Update dependency verify to 31.0.3

Todo List:

• Read the changed file (Directory.Packages.props)
• Analyze the dependency update scope and impact
• Check Verify library usage in the codebase
• Review for potential compatibility issues
• Provide comprehensive review feedback

---

Review Feedback

This is a clean, low-risk dependency update that follows good practices. Here's my analysis:

✅ Code Quality & Best Practices

• Proper use of centralized package management via Directory.Packages.props
• Clean patch version update (31.0.2 → 31.0.3) minimizes breaking change risk
• Automated dependency management via Renovate Bot ensures consistency

✅ Potential Issues Assessment

• No breaking changes expected: Patch versions in semantic versioning maintain backward compatibility
• Consistent pattern: Recent commits show similar dependency updates processed safely (see commits 2555928, fabfc23, etc.)
• Isolated change: Only the core Verify package version is updated

⚠️ Version Alignment Consideration

I noticed a potential inconsistency in your dependency versions:

Verify         31.0.3  ← Updated in this PR
Verify.NUnit   31.0.3  ← Already updated (commit 2555928)
Verify.TUnit   31.0.2  ← Still on older version (line 87)

Recommendation: Consider updating Verify.TUnit to 31.0.3 as well to maintain version alignment, though this isn't critical for functionality.

✅ Performance & Security

• Patch updates typically include bug fixes and minor performance improvements
• No security concerns with this update
• Verify library is extensively used for snapshot testing across the codebase

✅ Test Coverage

• TUnit's comprehensive test suite should catch any compatibility issues
• Verify is primarily used in test projects (TUnit.Core.SourceGenerator.Tests, TUnit.PublicAPI), reducing production risk
• The project follows good practices with snapshot testing validation per CLAUDE.md guidelines

Overall Assessment

✅ APPROVED - This is a safe, well-managed dependency update that should be merged.

---