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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.Extensions.DependencyInjection (source)	nuget	patch	10.0.0 -> 10.0.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]

PR Review: Dependency Update - Microsoft.Extensions.DependencyInjection 10.0.0 → 10.0.1

✅ Summary

This is a patch version update from Renovate Bot updating Microsoft.Extensions.DependencyInjection from 10.0.0 to 10.0.1. The changes are minimal and low-risk.

📋 Changes Reviewed

• Directory.Packages.props (line 36): Central package version updated
• TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj (line 12): Template project reference updated

✅ Code Quality

• Clean: Only version number changes, no code modifications
• Consistent: Both centrally managed package version and F# template reference are updated together
• Proper scope: Changes are appropriately limited to dependency declarations

✅ Best Practices

• ✅ Uses centralized package management (Directory.Packages.props)
• ✅ Template stays in sync with central dependency versions
• ✅ Follows semantic versioning (patch update only)

✅ Risk Assessment

Risk Level: LOW

Patch updates (10.0.0 → 10.0.1) typically contain:

• Bug fixes
• Performance improvements
• Security patches
• No breaking changes

✅ Security

No security concerns. Patch updates are generally recommended for:

• Bug fixes that may include edge case corrections
• Potential security improvements

✅ Testing Considerations

• Standard CI tests should be sufficient for a patch dependency update
• TUnit's extensive test suite (Engine.Tests, Assertions.Tests, etc.) will verify compatibility
• No dual-mode implementation concerns (this is just a dependency update)
• No snapshot updates needed (no code generation or API changes)

ℹ️ Notes

1. Automerge enabled: Per the PR description, this will auto-merge once CI passes
2. No code changes required: This is purely a dependency version bump
3. Template consistency: Good that the F# template project is kept in sync with the central package version

✅ Recommendation

APPROVE - This is a routine patch dependency update with no code changes. Once CI passes, this is safe to merge.

---

Review generated following TUnit development guidelines from CLAUDE.md

[Copilot]

Pull request overview

This PR updates the Microsoft.Extensions.DependencyInjection package from version 10.0.0 to 10.0.1 across the repository.

• Updates central package version management in Directory.Packages.props
• Updates the F# template project file to reflect the new version for template instantiation

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
Directory.Packages.props	Updates the centrally managed version of Microsoft.Extensions.DependencyInjection to 10.0.1, which will be inherited by all projects using central package management
TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj	Updates the explicit package version in the F# project template to 10.0.1 for standalone template instantiation

[claude]

🤖 PR Review - Automated Analysis

Summary

Dependency update: Microsoft.Extensions.DependencyInjection 10.0.0 → 10.0.1

---

✅ Review Results

Code Quality & Best Practices

• ✅ Clean, minimal changes appropriate for a dependency update
• ✅ Follows centralized package management pattern (Directory.Packages.props)
• ✅ Template project (F# test project) properly synchronized

Bugs & Issues

• ✅ No issues detected
• ✅ Patch version update should be fully backward-compatible
• ✅ No breaking changes expected

Performance

• ✅ Patch updates typically include performance improvements
• ✅ No negative impact expected

Security

• ✅ Keeping dependencies current is a security best practice
• ✅ Trusted Microsoft package source

Test Coverage

• ✅ No new code requiring tests
• ✅ Existing CI validation should catch any compatibility issues

CLAUDE.md Compliance

• ✅ No dual-mode implementation needed (dependency only)
• ✅ No snapshot updates required (no generator/API changes)
• ✅ All requirements satisfied

---

📊 Files Changed

1. Directory.Packages.props - Central version management
2. TUnit.Templates/content/TUnit.FSharp/TestProject.fsproj - Template synchronization

---

✅ Recommendation: APPROVE & MERGE

This is a routine maintenance update with minimal risk. The patch version bump from a trusted Microsoft dependency should integrate smoothly with existing functionality.

---

Automated review by Claude Code following TUnit development guidelines