chore(deps): update verify to 31.14.0

[thomhurst]

This PR contains the following updates:

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

---

Release Notes

VerifyTests/Verify (Verify)

v31.14.0

Compare Source

• #​1700 [TUnit] infrastructure fixtures appear in verified filenames / add VerifierSettings.IgnoreParameters
• #​1701 Support global IgnoreParameters setting
• #​1702 add IgnoreClassArguments

---

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 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.13.5 → 31.14.0

This is a straightforward Renovate Bot minor version bump for the Verify snapshot testing packages. The change is a 3-line diff in Directory.Packages.props only. Overall this looks correct, but there are a couple of observations worth noting.

What changes in 31.14.0

The release notes for this version highlight:

• #1700 — [TUnit] infrastructure fixtures appear in verified filenames / adds VerifierSettings.IgnoreParameters<T>
• #1701 — Support global IgnoreParameters setting
• #1702 — Add IgnoreClassArguments

Issue #1700 is directly relevant to TUnit: it specifically fixes a problem where TUnit infrastructure fixtures (e.g. [Before(TestDiscovery)] hooks, assembly-level fixtures) were leaking into Verify's verified filenames, causing spurious snapshot mismatches. This is a welcome fix for the TUnit ecosystem.

Observation: Verify.NUnit is declared but never used

Verify.NUnit is present in Directory.Packages.props as a centrally-managed version, but no .csproj in the repository contains a <PackageReference Include="Verify.NUnit" /> entry. The only places that reference Verify packages are:

• TUnit.Core.SourceGenerator.Tests — uses Verify + Verify.TUnit
• TUnit.Mocks.SourceGenerator.Tests — uses Verify + Verify.TUnit
• TUnit.Assertions.SourceGenerator.Tests — uses Verify + Verify.TUnit
• TUnit.PublicAPI — uses Verify + Verify.TUnit

Keeping an unused PackageVersion entry in Directory.Packages.props is harmless (it only pins a version without pulling a transitive reference), but it does create a small maintenance burden: future Renovate PRs will continue to bump a package that no project actually consumes. If Verify.NUnit was removed at some point as a direct dependency and never replaced with a PackageReference, the corresponding PackageVersion line could be cleaned up. That said, this is pre-existing and not introduced by this PR.

Snapshot test consideration

Because 31.14.0 changes how Verify resolves filenames when TUnit infrastructure fixtures are involved (issue #1700), there is a theoretical risk of verified filename format changes that could break existing .verified.txt snapshot files. In practice the fix is on the Verify side and should only affect scenarios where infrastructure fixture class names were previously bleeding into filenames — but it is worth confirming the CI snapshot tests pass green after merging, specifically for the source generator test projects.

Summary

The update is safe and beneficial. The Verify.NUnit unused entry is a pre-existing cosmetic issue worth cleaning up separately if desired. No snapshot file updates appear to be needed from this diff alone, but verifying the CI run is the right validation step.

[claude]

Dependency Update Review: Verify 31.13.5 to 31.14.0

This is a straightforward Renovate Bot minor version bump. The change is a 3-line diff in Directory.Packages.props only.

What changes in 31.14.0

The release notes highlight three items:

• Issue 1700 - [TUnit] infrastructure fixtures appear in verified filenames / adds VerifierSettings.IgnoreParameters
• PR 1701 - Support global IgnoreParameters setting
• PR 1702 - Add IgnoreClassArguments

Issue 1700 is directly relevant to TUnit: it fixes a problem where TUnit infrastructure fixtures (e.g. [Before(TestDiscovery)] hooks, assembly-level fixtures) were leaking into Verify verified filenames, causing spurious snapshot mismatches. This is a welcome fix for the ecosystem.

Observation: Verify.NUnit is declared but never used

Verify.NUnit is present in Directory.Packages.props as a centrally-managed version, but no .csproj in the repository contains a PackageReference for it. The four projects that use Verify packages (TUnit.Core.SourceGenerator.Tests, TUnit.Mocks.SourceGenerator.Tests, TUnit.Assertions.SourceGenerator.Tests, TUnit.PublicAPI) all reference only Verify and Verify.TUnit.

Keeping an unused PackageVersion entry is harmless in terms of build output, but it does create ongoing maintenance noise: Renovate will continue to file PRs bumping a version that no project actually consumes. This is pre-existing and not introduced by this PR, but it is a good candidate for a follow-up cleanup if Verify.NUnit was removed as a direct dependency at some point and the PackageVersion entry was never pruned.

Snapshot test consideration

Because 31.14.0 changes how Verify resolves filenames when TUnit infrastructure fixtures are involved, there is a theoretical risk of verified filename format changes that could affect existing .verified.txt files. The fix should only impact scenarios where infrastructure fixture class names were previously bleeding into filenames. Confirming CI snapshot tests pass green is the right validation.

Summary

The update is safe and beneficial. No issues with the diff itself. The Verify.NUnit unused entry is worth a follow-up cleanup but is out of scope for this PR.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

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