No nuget access #6783
Merged
No nuget access #6783
Conversation
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
Member
Author
Youssef1313
approved these changes
Oct 22, 2025
Youssef1313
reviewed
Oct 22, 2025
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.
Pipeline setting ensures that nuget.org access is completely blocked. To avoid restoring packages from there, even in tests.
To try this locally you can add this to hosts file (C:\Windows\System32\drivers\etc\hosts
The reference assemblies default restore will cache the restored packages in users temp, debug into ResolveAsync method, you will see where it grabs it from in ResolveAsyncCore.
Changes are not observable on the normal PR pipeline, but I've run build on internal pipeline. Unfortunately there is no public infra for 1es so we won't be able to get this into PR build as well, but it should be rare that we see this fail.