Bump Microsoft.Extensions.Logging from 10.0.8 to 10.0.9

[dependabot]

Updated Microsoft.Extensions.Logging from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.Extensions.Logging's releases.

No release notes found for this version range.

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)

[dependabot]

Superseded by #30.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The current changes introduce a version mismatch within the Microsoft.Extensions ecosystem. While automated analysis indicates the PR is up to standards, the logic review highlights a significant runtime risk associated with partial suite updates.

Updating these packages in isolation frequently results in TypeLoadException or assembly binding failures at runtime because the .NET logging and configuration abstractions are tightly coupled with their implementations. To ensure application stability, it is recommended to update the entire suite of Microsoft.Extensions.* packages to the same version simultaneously.

About this PR

• The project uses Central Package Management, but this PR updates libraries in isolation. When updating core .NET libraries like Microsoft.Extensions, it is best practice to update the entire suite together to prevent inconsistency across the dependency graph and potential resolution warnings.

Test suggestions

• Verify that the project compiles without errors following the package update.
• Verify that logging functionality operates correctly with the updated version.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the project compiles without errors following the package update.
2. Verify that logging functionality operates correctly with the updated version.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🟡 MEDIUM RISK}

Mixing versions within the Microsoft.Extensions suite (e.g., updating Logging while leaving Abstractions and Configuration on an older version) often results in runtime TypeLoadExceptions. Ensure all related packages in the suite are updated to the same version to maintain a consistent dependency graph.

Try running the following prompt in your coding agent:

Update all Microsoft.Extensions.* package versions in Directory.Packages.props to match the new version.