chore(deps): update verify to 31.15.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	31.14.0 → 31.15.0
Verify.NUnit	nuget	minor	31.14.0 → 31.15.0
Verify.TUnit	nuget	minor	31.14.0 → 31.15.0

---

Release Notes

VerifyTests/Verify (Verify)

v31.15.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• 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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[claude]

Dependency Update Review: Verify 31.14.0 → 31.15.0

This is a routine Renovate Bot dependency bump updating three Verify packages in Directory.Packages.props:

• Verify 31.14.0 → 31.15.0
• Verify.NUnit 31.14.0 → 31.15.0
• Verify.TUnit 31.14.0 → 31.15.0

What changed in 31.15.0

Looking at the commits between 31.14.0 and 31.15.0, the notable change is a rename: IgnoreClassArguments → IgnoreConstructorParameters (VerifyTests/Verify#1703). There are also minor internal updates (package bumps, allow empty string to ignore type in DerivePathInfo).

Assessment

No concerns. The change is correct and minimal — only the centralized Directory.Packages.props is touched, which is the right place for version management in a Central Package Management (CPM) setup.

A few things to be aware of given the 31.15.0 changes:

• The rename of IgnoreClassArguments → IgnoreConstructorParameters in Verify itself is unlikely to affect TUnit's usage since these packages are consumed as test infrastructure dependencies (snapshot testing in source generator tests), not as TUnit's own API. No call-sites in the repo appear to reference IgnoreClassArguments directly.
• The six projects consuming these packages (TUnit.Core.SourceGenerator.Tests, TUnit.Mocks.SourceGenerator.Tests, TUnit.Assertions.SourceGenerator.Tests, TUnit.PublicAPI, TUnit.Mocks.Assertions, TUnit.Assertions) should be unaffected since the renamed API is unlikely to be in use.

Verdict

This is a safe, low-risk minor update. The automerge configuration is appropriate for this type of change. Approve and merge.

[codacy-production]

Up to standards ✅

🟢 Issues0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics0 complexity

Metric	Results
Complexity	0

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}