Add dotnet12 feeds to NuGet.config - #11893
Merged
Merged
Conversation
The VMR (dotnet/dotnet) main branch now publishes its 11.0.0-rc.1.* assets to the dotnet12/dotnet12-transport feeds. WPF's NuGet.config only listed feeds up to dotnet11, so codeflow PR #11869 failed restore with NU1102 on Microsoft.NETCore.App.{Ref,Runtime.win-*,Host.win-*} 11.0.0-rc.1.26452.110. dotnet/winforms already carries these two sources. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
subhajitm
marked this pull request as ready for review
September 4, 2026 09:30
dipeshmsft
approved these changes
Sep 4, 2026
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The change is a minimal, well-scoped NuGet feed addition that aligns with the stated restore failure cause and does not alter build logic.
Pull request overview
This PR updates the repository’s NuGet.config package sources to include the dotnet12 and dotnet12-transport Azure DevOps feeds so restores can resolve newly published VMR (dotnet/dotnet main) assets that are no longer present on dotnet11 feeds.
Changes:
- Add
dotnet12package source. - Add
dotnet12-transportpackage source.
File summaries
| File | Description |
|---|---|
| NuGet.config | Adds dotnet12 and dotnet12-transport feeds to unblock restores that require packages published to those sources. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
pranav-gupta-msft
approved these changes
Sep 4, 2026
harshit7962
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Codeflow PR #11869 (
[main] Source code updates from dotnet/dotnet) fails restore on every leg:Same for
Microsoft.NETCore.App.Runtime.win-{x86,x64,arm64}andMicrosoft.NETCore.App.Host.win-{x86,x64,arm64}.Cause
The VMR (
dotnet/dotnetmain) now publishes its11.0.0-rc.1.*assets to thedotnet12anddotnet12-transportfeeds. OurNuGet.configonly lists feeds up todotnet11, so those packages are unreachable.Verified against the live feeds:
11.0.0-rc.1.26452.110on any of the 14 feeds we list11.0.0-rc.1.26411.119(whatmainuses today)dotnet11rc.1available ondotnet1111.0.0-rc.1.26431.11811.0.0-rc.1.26452.110ondotnet12Microsoft.Private.Winforms 11.0.0-rc.1.26452.110dotnet12-transportdotnet/winformsNuGet.configdotnet12feedsThis is not a version-number problem and not a source bug — the referenced assets exist, just on a feed we do not consume yet.
Fix
Add the two
dotnet12sources, matching whatdotnet/winformsalready carries.Validation
Applied on top of #11869 locally and ran
Restore.cmd -cifor x86, x64 and arm64 — all three succeeded with 0 errors. All seven previously-NU1102packages resolve at11.0.0-rc.1.26452.110, and.nupkg.metadataconfirmsdotnet12as the source.Notes
NuGet.configis meant to stay in sync with thedotnet-wpf-intrepo; matching PRs are being raised there and indnceng/internal/dotnet-wpf.mainrather than editing the maestro-owned codeflow branch, since darc would overwrite hand-edits there. This unblocks every futuremaincodeflow, not just [main] Source code updates from dotnet/dotnet #11869.Microsoft Reviewers: Open in CodeFlow