fix(nuget): repo nuget.config breaks corporate packageSourceMapping setups - #5
Merged
Merged
Conversation
…etups Renames the source key from `nuget` to `nuget.org` (the de-facto standard name) and adds an explicit `<packageSourceMapping>` block that clears inherited rules and routes all packages to nuget.org. Without this, any contributor or CI agent whose user-level NuGet.Config contains a `packageSourceMapping` block keyed to `nuget.org` (very common in enterprise setups) gets a fully broken restore with cryptic NU1100 errors, because mapping is keyed by source name and the prior `nuget` key did not match. Verified by restoring against a corporate NuGet.Config with active source mapping — succeeds where previously every project failed. Refs #2 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 21, 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
1 participant
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.
Summary
Closes #2.
The repo's
nuget.configregistered nuget.org under the source namenugetand provided nopackageSourceMappingblock. Any contributor or CI agent with a user-levelNuGet.Configcontaining apackageSourceMappingblock keyed tonuget.org(extremely common in enterprise setups) gets a fully broken restore with cryptic NU1100 errors — because source mapping is keyed by source name, not URL.Two changes:
nuget→nuget.org(de-facto standard).<packageSourceMapping>with<clear/>+ wildcard →nuget.org. This wins over any inherited user-level mapping, so the repo is now immune to corporate config drift.Tiny diff (+7/-1). Belt-and-braces — either change alone would help, both together are bulletproof.
Test plan
dotnet restore nuke-common.slnxagainst a real corporateNuGet.Configwith activepackageSourceMapping— succeeds where previously every project failed with NU1100🤖 Generated with Claude Code