Bump Verify.XunitV3 from 31.20.0 to 31.27.0

[dependabot]

Updated Verify.XunitV3 from 31.20.0 to 31.27.0.

Release notes

Sourced from Verify.XunitV3's releases.

31.27.0

• #​1809 Emit received→verified mapping for out-of-process accept/review tooling
• #​1810 Allow a stream target for a text extension
• #​1812 Received map file

31.26.0

• #​1664 GuidScrubber support N format
• #​1803 Expose ssim
• #​1804 Span based scrubbers
• #​1805 Use ordinal string comparisons
• #​1806 N format guids
• #​1807 Align received naming single tfm
• #​1808 Fix unique directory received multi tfm

31.25.0

• #​1758 UseProjectRelative + SourceFileRelativeDirectory
• #​1800 Add mirror source structure for verified files

31.24.3

• #​1799 Better line ending failure diagnostics

31.24.2

• #​1794 Normalize scrubbed-to-empty text to emptyString
• #​1798 Bump package references

31.24.1

• #​1790 Only load referenced plugins

31.24.0

• #​1789 Add ExcludeTargets with converter-side IsTargetExcluded check

31.23.0

• #​1785 Fix chunk boundary scrubber bugs and test adapter defects
• #​1788 Add exclude targets to omit targets by extension

31.22.0

• #​1778 Allow conversion splitters for text extensions
• #​1779 Fix chunk boundary scrubber bugs and test adapter defects
• #​1781 stop using MSTest metapackage
• #​1782 Migrate CI to Microsoft.Testing.Platform so all tests run
• #​1783 Guard against duplicate xunit attachment names
• #​1784 Add Kill process locking file option

31.21.0

• #​1656 throw for greedy RegisterFileConverter
• #​1762 Reject carriage returns in verified files instead of normalizing
• #​1767 Fix correctness and perf issues in compare, recording, naming and checks
• #​1768 Fix VerifySettings copy constructor, temp cleanup, and stream/extensi…
• #​1769 Fix combination runner/converter, Expecto directory verification, and…
• #​1770 Fix serialization scrub/convert bugs and reduce per-value scrubbing allocations
• #​1771 Fix verifier cleanup composition, stream/xml disposal and comparison
• #​1772 Bump Argon from 0.34.0 to 0.35.0
• #​1773 Bump DiffEngine from 19.2.0 to 19.3.0
• #​1774 Clear synchronization context in to task()
• #​1775 Throw for greedy RegisterFileConverter

  Commits viewable in compare view.

  

  Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

  ---

  Dependabot commands and options

  
  

  You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Warning

Review limit reached

@dependabot[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 463256e5-b5e9-402a-a294-f31b30c08b27

📥 Commits

Reviewing files that changed from the base of the PR and between cf7d9d6 and 43f6dd3.

📒 Files selected for processing (1)

• Directory.Packages.props

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/nuget/Verify.XunitV3-31.27.0

---

_{Comment @coderabbitai help to get the list of available commands.}

[coveralls]

Coverage Report for CI Build 30086253377

Coverage decreased (-2.0%) to 93.813%

Details

• Coverage decreased (-2.0%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• 48 coverage regressions across 1 file.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

48 previously-covered lines in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
src/Common/ITypeSymbolExtensions.cs	48	72.85%

---

Coverage Stats

Relevant Lines:	1584
Covered Lines:	1486
Line Coverage:	93.81%
Coverage Strength:	3.75 hits per line

---

💛 - Coveralls