Remove audit sources from NuGet.config #120696
Merged
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
The api.nuget.org source will clash with the CFSClean network isolation policy
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR removes the audit sources configuration from NuGet.config to resolve network isolation policy conflicts. The api.nuget.org source in the audit configuration was clashing with the CFSClean network isolation policy.
Key Changes
- Removed the entire
<auditSources>section from NuGet.config - Eliminated the reference to api.nuget.org that was causing network policy conflicts
github-actions
bot
added
the
needs-area-label
ViktorHofer
approved these changes
Oct 14, 2025
akoeplinger
added
area-Infrastructure
and removed
needs-area-label
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
This was referenced Oct 14, 2025
jkoritzinsky
approved these changes
Oct 14, 2025
Member
Author
|
/backport to release/10.0 |
Contributor
|
Started backporting to |
4 tasks
Member
Author
|
/backport to release/9.0-staging |
Contributor
|
Started backporting to |
4 tasks
akoeplinger
added a commit
that referenced
this pull request
Nov 7, 2025
Backport of #120696 to release/9.0-staging /cc @akoeplinger ## Customer Impact - [ ] Customer reported - [X] Found internally no customer impact, this affects our internal builds due to CFS restrictions. ## Regression - [ ] Yes - [X] No ## Testing Tested in CI. ## Risk None. This just changes a setting for nuget package restore. **IMPORTANT**: If this backport is for a servicing release, please verify that: - For .NET 8 and .NET 9: The PR target branch is `release/X.0-staging`, not `release/X.0`. - For .NET 10+: The PR target branch is `release/X.0` (no `-staging` suffix). ## Package authoring no longer needed in .NET 9 **IMPORTANT**: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version. Keep in mind that we still need package authoring in .NET 8 and older versions. Co-authored-by: Alexander Köplinger <[email protected]>
hoyosjs
pushed a commit
that referenced
this pull request
Nov 7, 2025
Backport of #120696 to release/10.0 /cc @akoeplinger ## Customer Impact - [ ] Customer reported - [x] Found internally no customer impact, this affects our internal builds due to CFS restrictions. ## Regression - [ ] Yes - [x] No ## Testing Tested in CI. ## Risk None. This just changes a setting for nuget package restore. **IMPORTANT**: If this backport is for a servicing release, please verify that: - For .NET 8 and .NET 9: The PR target branch is `release/X.0-staging`, not `release/X.0`. - For .NET 10+: The PR target branch is `release/X.0` (no `-staging` suffix). ## Package authoring no longer needed in .NET 9 **IMPORTANT**: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version. Keep in mind that we still need package authoring in .NET 8 and older versions. Co-authored-by: Alexander Köplinger <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.