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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
xunit.v3.extensibility.core	nuget	patch	3.2.0 -> 3.2.1

---

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

Overview

This PR updates xunit.v3.extensibility.core from version 3.2.0 to 3.2.1 - a patch version increment that should be low-risk.

---

✅ Code Quality & Best Practices

Good practices observed:

• Using centralized package management via Directory.Packages.props
• Automated dependency updates via Renovate Bot
• Patch version update (minimal breaking change risk)

---

⚠️ Potential Issues Identified

1. Version Inconsistency (Medium Priority)

The xunit v3 packages are now at inconsistent versions:

• xunit.v3: 3.2.0 (outdated)
• xunit.v3.assert: 3.2.1 ✓
• xunit.v3.extensibility.core: 3.2.1 ✓ (this PR)

Recommendation: Update xunit.v3 to 3.2.1 for consistency.

2. Hardcoded Version References (Low Priority)

Test files contain hardcoded version references that may need updating:

TUnit.Analyzers.Tests/Verifiers/CSharpCodeFixVerifier'2.cs:45:

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

TUnit.Analyzers.Tests/XUnitMigrationAnalyzerTests.cs:358:

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

Impact: These are using 3.0.1 (very old version) for test purposes. Consider if these should be updated or if the old version is intentionally used for compatibility testing.

---

🔒 Security Considerations

Assessment: LOW RISK

• Patch version update from trusted source (xUnit project)
• No known security vulnerabilities in either version
• Dependency only used in test/analyzer code, not production runtime

---

⚡ Performance Considerations

Assessment: NEUTRAL

• Patch updates typically focus on bug fixes
• No performance impact expected from this change
• Test execution performance should remain unchanged

---

🧪 Test Coverage

Current state:

• Package is used in analyzer tests for xUnit migration functionality
• Tests should continue to work with patch update
• No additional test coverage needed

Recommendation: Run the analyzer test suite to ensure compatibility, particularly:

• TUnit.Analyzers.Tests
• Tests that use the ConfigureXUnitTest helper method

---

📋 Action Items

1. Consider updating xunit.v3 to 3.2.1 for version consistency
2. Review hardcoded version references in test files (decide if intentional)
3. Run tests to verify analyzer functionality remains intact
4. Monitor for any test failures in CI

---

✅ Overall Recommendation

APPROVE - This is a low-risk patch update that maintains compatibility and brings version alignment with other xunit v3 packages. The automated Renovate process is working correctly.

The identified issues are minor and don't block this update, but should be considered for future improvements.