chore(deps): update microsoft.extensions#6211
Conversation
There was a problem hiding this comment.
Code Review
This is a clean, automated Renovate dependency bump — nothing to flag. All changes are mechanical version string increments across 6 files:
- **** — centralized version bumps for (patch)
- **** and **** — the per-TFM
Versionattribute updated to match (theVersionOverridevalues correctly stay at the per-framework resolved versions, which is intentional and correct) - **** / **** —
Microsoft.Extensions.Http.ResilienceandMicrosoft.Extensions.ServiceDiscoverybumped10.6.0 → 10.7.0(minor) - **** —
Microsoft.Extensions.DependencyInjectionpinned version updated to match
All updates are consistent — no version split across files, no skipped packages, no stale pins left behind. The VersionOverride pattern in the multi-TFM projects (keeping the resolved version per framework while bumping the listed version) is the correct idiom here.
✅ Looks good to merge.
There was a problem hiding this comment.
Code Review
This is a clean, automated Renovate dependency bump — nothing to flag. All changes are mechanical version string increments across 6 files:
- Directory.Packages.props — centralized version bumps for Microsoft.Extensions.{DependencyInjection,Http,Logging,Logging.Abstractions} 10.0.8 to 10.0.9 (patch)
- TUnit.Logging.Microsoft.csproj and TUnit.Mocks.Logging.csproj — the per-TFM Version attribute updated to match (the VersionOverride values correctly stay at per-framework resolved versions, which is intentional)
- ExampleNamespace.ServiceDefaults.csproj / CloudShop.ServiceDefaults.csproj — Microsoft.Extensions.Http.Resilience and Microsoft.Extensions.ServiceDiscovery bumped 10.6.0 to 10.7.0 (minor)
- TestProject.fsproj — Microsoft.Extensions.DependencyInjection pinned version updated to match
All updates are consistent — no version split across files, no skipped packages, no stale pins left behind. The VersionOverride pattern in the multi-TFM projects (keeping the resolved version per framework while bumping the listed version) is the correct idiom here.
Looks good to merge.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This PR contains the following updates:
10.0.8→10.0.910.0.8→10.0.910.6.0→10.7.010.0.8→10.0.910.0.8→10.0.910.6.0→10.7.0Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate.