Skip to content

chore(deps): raise the Microsoft.Extensions family past the downgrade - #532

Merged
mrviduus merged 1 commit into
mainfrom
fix/dotnet-package-versions
Sep 2, 2026
Merged

chore(deps): raise the Microsoft.Extensions family past the downgrade#532
mrviduus merged 1 commit into
mainfrom
fix/dotnet-package-versions

Conversation

@mrviduus

@mrviduus mrviduus commented Sep 2, 2026

Copy link
Copy Markdown
Owner

Two Dependabot PRs were failing on the same error, and neither of them was the cause:

#529  ModelContextProtocol 2.2.0 -> Microsoft.Extensions.Hosting.Abstractions (>= 10.0.10)
#524  Microsoft.Extensions.Http 10.0.11 -> ... Diagnostics 10.0.11

NU1109, detected package downgrade. Directory.Packages.props pinned the Microsoft.Extensions.*
family at 10.0.8, so anything reaching for a newer one transitively could not restore.

Central package management is what made both PRs fail — and it is also why one edit fixes both.
That is the trade, visible from both sides in the same afternoon.

Ten pins raised to 10.0.11. Deliberately not touching the AspNetCore or EntityFrameworkCore
pins still on 10.0.8: different families, not implicated in either error, and moving them would
widen this past what was diagnosed. Microsoft.Extensions.AI stays on its own 10.6.0 line.

Verification

dotnet restore clean, Release build succeeds, 886 unit tests pass.

Once this lands, #524 and #529 should rebase green on their own.

Rollback

Revert. Both Dependabot PRs go back to failing at restore.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MkGcwmi1fuGCBLmGwdEZ1F

Two Dependabot PRs were failing on the same thing, and neither of them
was the problem:

  #529: ModelContextProtocol 2.2.0 -> Microsoft.Extensions.Hosting.Abstractions (>= 10.0.10)
  #524: Microsoft.Extensions.Http 10.0.11 -> Diagnostics 10.0.11

NU1109, detected package downgrade. Directory.Packages.props pinned the
Microsoft.Extensions.* family at 10.0.8, and anything that reached for a
newer one transitively could not restore. Central package management is
what made both PRs fail; it is also why one edit fixes both.

Ten pins raised to 10.0.11. Deliberately not touching the AspNetCore or
EntityFrameworkCore pins still on 10.0.8 — different families, not
implicated in either error, and moving them would widen this past what
was diagnosed. Microsoft.Extensions.AI stays on its own 10.6.0 line.

Verified: restore, Release build, 886 unit tests.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MkGcwmi1fuGCBLmGwdEZ1F
@mrviduus
mrviduus enabled auto-merge (squash) September 2, 2026 04:08
@mrviduus
mrviduus merged commit f1c91b5 into main Sep 2, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant