chore(deps): update dependency xunit.v3.extensibility.core to 3.1.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
xunit.v3.extensibility.core	nuget	minor	3.0.1 -> 3.1.0

---

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

---

Pull Request Review: xunit.v3.extensibility.core Update

Todo List

• Read and analyze the changed file
• Check for xunit usage in the codebase
• Review potential impact on tests and code
• Assess security and performance implications
• Provide comprehensive review feedback

---

Review Summary

This PR updates xunit.v3.extensibility.core from version 3.0.1 to 3.1.0 in the central package management file Directory.Packages.props:96.

Code Quality & Best Practices ✅

• Centralized Package Management: The change follows good practices by using centralized package version management via Directory.Packages.props
• Semantic Versioning: This is a minor version update (3.0.1 → 3.1.0) which should be backward compatible

Critical Issues Found ⚠️

Hardcoded Version References: The codebase contains hardcoded references to the old version 3.0.1 that need to be updated:

1. XUnitMigrationAnalyzerTests.cs:637 and :649:

   new PackageIdentity("xunit.v3.extensibility.core", "3.0.1")

2. CSharpCodeFixVerifier.cs:45:

   .AddPackages([new PackageIdentity("xunit.v3.extensibility.core", "3.0.1")])

Impact Assessment

• Test Coverage: The hardcoded versions in test files will cause version mismatches between the actual dependency (3.1.0) and test expectations (3.0.1)
• Analyzer Tests: The XUnit migration analyzer tests specifically use the old version, which could lead to inconsistent behavior
• Build/CI: Tests may fail or behave unexpectedly due to version mismatches

Security Considerations ✅

• Minor version updates typically contain bug fixes and improvements
• No known security concerns with this specific xunit.v3 update
• Updating dependencies is generally a good security practice

Performance Considerations ✅

• Minor version updates often include performance improvements
• No breaking changes expected in minor version bumps
• Impact should be positive or neutral

Recommendations

This PR requires additional changes to maintain consistency:

1. Update hardcoded version references in:

   • /TUnit.Analyzers.Tests/XUnitMigrationAnalyzerTests.cs (lines 637, 649)
   • /TUnit.Analyzers.Tests/Verifiers/CSharpCodeFixVerifier2.cs` (line 45)

2. Run tests after updating hardcoded references to ensure compatibility

3. Consider using a constant for the xunit version to avoid future inconsistencies

Action Required

Do not merge until the hardcoded version references are updated to match the new version (3.1.0).