chore(deps): update dependency microsoft.extensions.dependencyinjection to 9.0.9

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.Extensions.DependencyInjection (source)	nuget	patch	9.0.8 -> 9.0.9

---

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

---

PR Review: Microsoft.Extensions.DependencyInjection Update

Todo List:

• Read changed files to understand the update scope
• Analyze the dependency version change (9.0.8 → 9.0.9)
• Review code quality and best practices
• Assess potential bugs or issues
• Evaluate performance considerations
• Check security concerns
• Consider test coverage implications
• Provide comprehensive review feedback

Analysis Summary:

This PR updates Microsoft.Extensions.DependencyInjection from version 9.0.8 to 9.0.9 in two locations:

1. Directory.Packages.props:36 - Central package management
2. TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj:12 - F# template project

Review Feedback

✅ Code Quality and Best Practices

• Excellent: The changes follow proper centralized package management patterns using Directory.Packages.props
• Consistent: Both locations are updated in sync (central management + F# template)
• Clean: No unnecessary changes or modifications beyond the version bump

✅ Potential Bugs or Issues

• Low Risk: This is a patch version update (9.0.8 → 9.0.9) which should only include bug fixes and minor improvements
• Breaking Changes: Patch versions follow semantic versioning - no breaking changes expected
• Compatibility: No API changes anticipated that would affect TUnit's usage

✅ Performance Considerations

• Positive Impact: Patch updates often include performance optimizations and bug fixes
• Minimal Overhead: Dependency injection performance improvements are typically included in patch releases
• No Concerns: No performance regressions expected from a patch update

✅ Security Concerns

• Security Patches: Patch versions often include important security fixes
• Trusted Source: Microsoft.Extensions packages are well-maintained and security-audited
• Supply Chain: Updates from official Microsoft packages carry low supply chain risk

✅ Test Coverage

• Existing Tests: TUnit's comprehensive test suite should catch any regressions
• Recommendation: Run the full test suite to ensure compatibility:

  dotnet test
  dotnet test TUnit.Core.SourceGenerator.Tests
  dotnet test TUnit.PublicAPI

• Template Testing: The F# template change should be validated if template tests exist

Recommendation: ✅ APPROVE

This is a straightforward, low-risk dependency patch update that:

• ✅ Follows proper package management practices
• ✅ Includes both central management and template consistency
• ✅ Brings potential bug fixes and security updates
• ✅ Has minimal risk of introducing breaking changes

Next Steps:

1. Ensure CI tests pass completely
2. Consider running any template-specific tests if available
3. This PR can be safely merged once tests confirm compatibility