Remove audit sources from NuGet.config by akoeplinger · Pull Request #120696 · dotnet/runtime

akoeplinger · 2025-10-14T14:58:19Z

The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.

The api.nuget.org source will clash with the CFSClean network isolation policy

Copilot

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

dotnet-policy-service · 2025-10-14T15:31:43Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2025-11-06T21:03:51Z

/backport to release/10.0

github-actions · 2025-11-06T21:04:04Z

Started backporting to release/10.0 (link to workflow run)

akoeplinger · 2025-11-06T22:45:50Z

/backport to release/9.0-staging

github-actions · 2025-11-06T22:45:59Z

Started backporting to release/9.0-staging (link to workflow run)

@akoeplinger

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 <alex.koeplinger@outlook.com>

@akoeplinger

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 <alex.koeplinger@outlook.com>

ericstj · 2026-04-22T03:57:02Z

I heard from NuGet team that this is fixed, we can use https://data.nuget.org/v3/index.json

akoeplinger · 2025-10-14T14:58:19Z

The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.

The api.nuget.org source will clash with the CFSClean network isolation policy

Copilot

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

dotnet-policy-service · 2025-10-14T15:31:43Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2025-11-06T21:03:51Z

/backport to release/10.0

github-actions · 2025-11-06T21:04:04Z

Started backporting to release/10.0 (link to workflow run)

akoeplinger · 2025-11-06T22:45:50Z

/backport to release/9.0-staging

github-actions · 2025-11-06T22:45:59Z

Started backporting to release/9.0-staging (link to workflow run)

@akoeplinger

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 <alex.koeplinger@outlook.com>

@akoeplinger

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 <alex.koeplinger@outlook.com>

ericstj · 2026-04-22T03:57:02Z

I heard from NuGet team that this is fixed, we can use https://data.nuget.org/v3/index.json

akoeplinger · 2025-10-14T14:58:19Z

The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.

The api.nuget.org source will clash with the CFSClean network isolation policy

Copilot

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

dotnet-policy-service · 2025-10-14T15:31:43Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2025-11-06T21:03:51Z

/backport to release/10.0

github-actions · 2025-11-06T21:04:04Z

Started backporting to release/10.0 (link to workflow run)

akoeplinger · 2025-11-06T22:45:50Z

/backport to release/9.0-staging

github-actions · 2025-11-06T22:45:59Z

Started backporting to release/9.0-staging (link to workflow run)

@akoeplinger

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 <alex.koeplinger@outlook.com>

@akoeplinger

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 <alex.koeplinger@outlook.com>

ericstj · 2026-04-22T03:57:02Z

I heard from NuGet team that this is fixed, we can use https://data.nuget.org/v3/index.json

akoeplinger · 2025-10-14T14:58:19Z

The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.

The api.nuget.org source will clash with the CFSClean network isolation policy

Copilot

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

dotnet-policy-service · 2025-10-14T15:31:43Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2025-11-06T21:03:51Z

/backport to release/10.0

github-actions · 2025-11-06T21:04:04Z

Started backporting to release/10.0 (link to workflow run)

akoeplinger · 2025-11-06T22:45:50Z

/backport to release/9.0-staging

github-actions · 2025-11-06T22:45:59Z

Started backporting to release/9.0-staging (link to workflow run)

@akoeplinger

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 <alex.koeplinger@outlook.com>

@akoeplinger

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 <alex.koeplinger@outlook.com>

ericstj · 2026-04-22T03:57:02Z

I heard from NuGet team that this is fixed, we can use https://data.nuget.org/v3/index.json

akoeplinger · 2025-10-14T14:58:19Z

The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.

The api.nuget.org source will clash with the CFSClean network isolation policy

Copilot

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

dotnet-policy-service · 2025-10-14T15:31:43Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2025-11-06T21:03:51Z

/backport to release/10.0

github-actions · 2025-11-06T21:04:04Z

Started backporting to release/10.0 (link to workflow run)

akoeplinger · 2025-11-06T22:45:50Z

/backport to release/9.0-staging

github-actions · 2025-11-06T22:45:59Z

Started backporting to release/9.0-staging (link to workflow run)

@akoeplinger

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 <alex.koeplinger@outlook.com>

@akoeplinger

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 <alex.koeplinger@outlook.com>

ericstj · 2026-04-22T03:57:02Z

I heard from NuGet team that this is fixed, we can use https://data.nuget.org/v3/index.json

akoeplinger · 2025-10-14T14:58:19Z

The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.

The api.nuget.org source will clash with the CFSClean network isolation policy

Copilot

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

dotnet-policy-service · 2025-10-14T15:31:43Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2025-11-06T21:03:51Z

/backport to release/10.0

github-actions · 2025-11-06T21:04:04Z

Started backporting to release/10.0 (link to workflow run)

akoeplinger · 2025-11-06T22:45:50Z

/backport to release/9.0-staging

github-actions · 2025-11-06T22:45:59Z

Started backporting to release/9.0-staging (link to workflow run)

@akoeplinger

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 <alex.koeplinger@outlook.com>

@akoeplinger

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 <alex.koeplinger@outlook.com>

ericstj · 2026-04-22T03:57:02Z

I heard from NuGet team that this is fixed, we can use https://data.nuget.org/v3/index.json

akoeplinger · 2025-10-14T14:58:19Z

The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.

The api.nuget.org source will clash with the CFSClean network isolation policy

Copilot

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

dotnet-policy-service · 2025-10-14T15:31:43Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2025-11-06T21:03:51Z

/backport to release/10.0

github-actions · 2025-11-06T21:04:04Z

Started backporting to release/10.0 (link to workflow run)

akoeplinger · 2025-11-06T22:45:50Z

/backport to release/9.0-staging

github-actions · 2025-11-06T22:45:59Z

Started backporting to release/9.0-staging (link to workflow run)

@akoeplinger

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 <alex.koeplinger@outlook.com>

@akoeplinger

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 <alex.koeplinger@outlook.com>

ericstj · 2026-04-22T03:57:02Z

I heard from NuGet team that this is fixed, we can use https://data.nuget.org/v3/index.json

akoeplinger · 2025-10-14T14:58:19Z

The api.nuget.org source will clash with the CFSClean network isolation policy and the same data is provided by AzDO now.

The api.nuget.org source will clash with the CFSClean network isolation policy

Copilot

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

dotnet-policy-service · 2025-10-14T15:31:43Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2025-11-06T21:03:51Z

/backport to release/10.0

github-actions · 2025-11-06T21:04:04Z

Started backporting to release/10.0 (link to workflow run)

akoeplinger · 2025-11-06T22:45:50Z

/backport to release/9.0-staging

github-actions · 2025-11-06T22:45:59Z

Started backporting to release/9.0-staging (link to workflow run)

@akoeplinger

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 <alex.koeplinger@outlook.com>

@akoeplinger

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 <alex.koeplinger@outlook.com>

ericstj · 2026-04-22T03:57:02Z

I heard from NuGet team that this is fixed, we can use https://data.nuget.org/v3/index.json

Remove audit sources from NuGet.config
31ec83b
The api.nuget.org source will clash with the CFSClean network isolation policy

akoeplinger requested review from ViktorHofer and Copilot October 14, 2025 14:58

CopilotAI reviewed Oct 14, 2025
View reviewed changes

dotnet-policy-serviceBot assigned akoeplinger Oct 14, 2025

github-actionsBot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Oct 14, 2025

ViktorHofer approved these changes Oct 14, 2025
View reviewed changes

akoeplinger added area-Infrastructure and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Oct 14, 2025

github-project-automationBot added this to Runtime Infra Oct 14, 2025

This was referenced Oct 14, 2025
Test failure: System.IO.Tests.FileInfo_SymbolicLinks.ResolveLinkTarget_Succeeds #120380
Closed
Assert Interop.Sys.LSeek(this, 0, Interop.Sys.SeekWhence.SEEK_CUR) >= 0 in System.Net.XXX tests #120577
Closed

jkoritzinsky approved these changes Oct 14, 2025
View reviewed changes

agocke merged commit f9fce60 into mainOct 15, 2025
151 of 153 checks passed

github-project-automationBot moved this to Done in Runtime Infra Oct 15, 2025

agocke deleted the akoeplinger-patch-2 branch October 15, 2025 01:10

dotnet-maestroBot mentioned this pull request Oct 15, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#2885
Merged

github-actionsBot mentioned this pull request Nov 6, 2025
[release/10.0] Remove audit sources from NuGet.config #121419
Merged
4 tasks

github-actionsBot mentioned this pull request Nov 6, 2025
[release/9.0-staging] Remove audit sources from NuGet.config #121426
Merged
4 tasks

github-actionsBot locked and limited conversation to collaborators Dec 7, 2025