chore(deps): update dependency verify to 30.17.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	30.16.0 -> 30.17.0

---

Release Notes

VerifyTests/Verify (Verify)

v30.17.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

Reviewing this dependency update PR for:

• Code quality and best practices
• Potential bugs or issues
• Performance considerations
• Security concerns
• Test coverage

Review Summary

This is a straightforward dependency update for the Verify package from version 30.16.0 to 30.17.0. Based on my analysis:

✅ Approved - Low Risk Update

Code Quality & Best Practices:

• ✅ Clean update following centralized package management via Directory.Packages.props
• ✅ Proper version increment (minor version bump)
• ✅ No code changes required - purely dependency update

Potential Issues:

• ⚠️ Version Mismatch: I notice Verify.NUnit and Verify.TUnit packages are still at version 30.16.0 while the main Verify package is being updated to 30.17.0. This could potentially cause compatibility issues.
• ✅ No breaking changes expected for minor version bump
• ✅ Single line change minimizes risk of introducing bugs

Performance Considerations:

• ✅ Minor version updates typically include bug fixes and small improvements
• ✅ No performance regressions expected
• ✅ Verify is used primarily in test projects, so minimal impact on production performance

Security:

• ✅ Dependency updates generally include security fixes
• ✅ No security concerns with this update
• ✅ Coming from trusted source (VerifyTests organization)

Test Coverage:

• ✅ Verify package is extensively used across the test suite (TUnit.Core.SourceGenerator.Tests, TUnit.PublicAPI, etc.)
• ✅ Existing snapshot tests will validate the update
• ⚠️ Should run snapshot tests to ensure no unexpected changes

Recommendations:

1. Consider updating related packages: Update Verify.NUnit and Verify.TUnit to 30.17.0 (or latest compatible versions) to maintain consistency:

   <PackageVersion Include="Verify.NUnit" Version="30.17.0" />
   <PackageVersion Include="Verify.TUnit" Version="30.17.0" />

2. Run snapshot tests: Execute dotnet test TUnit.Core.SourceGenerator.Tests to ensure no snapshot changes or test failures

3. Verify compatibility: The minor version bump should be safe, but monitor for any test failures in CI

Verdict: ✅ LGTM with minor suggestion

This is a safe dependency update that follows best practices. The only consideration is keeping related Verify packages in sync for consistency, though this isn't strictly required for functionality.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Dependency Update

Reviewing this dependency update PR for:

• Code quality and best practices
• Potential bugs or issues
• Performance considerations
• Security concerns
• Test coverage

Review Summary

This is a straightforward dependency update for the Verify package from version 30.16.0 to 30.17.0. Based on my analysis:

✅ Approved - Low Risk Update

Code Quality & Best Practices:

• ✅ Clean update following centralized package management via Directory.Packages.props
• ✅ Proper version increment (minor version bump)
• ✅ No code changes required - purely dependency update

Potential Issues:

• ⚠️ Version Mismatch: I notice Verify.TUnit package is still at version 30.16.0 (line 90) while the main Verify package is being updated to 30.17.0 and Verify.NUnit is already at 30.17.0 (line 86). This could potentially cause compatibility issues.
• ✅ No breaking changes expected for minor version bump
• ✅ Single line change minimizes risk of introducing bugs

Performance Considerations:

• ✅ Minor version updates typically include bug fixes and small improvements
• ✅ No performance regressions expected
• ✅ Verify is used primarily in test projects (TUnit.Core.SourceGenerator.Tests, TUnit.PublicAPI, etc.), so minimal impact on production performance

Security:

• ✅ Dependency updates generally include security fixes
• ✅ No security concerns with this update
• ✅ Coming from trusted source (VerifyTests organization)

Test Coverage:

• ✅ Verify package is extensively used across the test suite (TUnit.Core.SourceGenerator.Tests, TUnit.PublicAPI, etc.)
• ✅ Existing snapshot tests will validate the update
• ⚠️ Should run snapshot tests to ensure no unexpected changes: dotnet test TUnit.Core.SourceGenerator.Tests

Recommendations:

1. Consider updating related packages: Update Verify.TUnit to 30.17.0 to maintain consistency:

   <PackageVersion Include="Verify.TUnit" Version="30.17.0" />

   This would align all Verify-related packages at the same version.

2. Run snapshot tests: Execute dotnet test TUnit.Core.SourceGenerator.Tests to ensure no snapshot changes or test failures per TUnit's development guidelines in CLAUDE.md

3. Verify compatibility: The minor version bump should be safe, but monitor for any test failures in CI

Verdict: ✅ LGTM with minor suggestion

This is a safe dependency update that follows best practices. The only consideration is keeping the Verify.TUnit package in sync for consistency, though this isn't strictly required for functionality.

---