Skip to content

fix(pipelines): allow public feed access for NuGet.org publish - #3366

Merged
Dmitry Gozman (dgozman) merged 1 commit into
microsoft:mainfrom
dgozman:fix-network-isolation-nuget-publish
Sep 21, 2026
Merged

Dmitry Gozman (dgozman) merged 1 commit into
microsoft:mainfrom
dgozman:fix-network-isolation-nuget-publish

Conversation

@dgozman

Copy link
Copy Markdown
Collaborator

Summary

  • The release pipeline (build 15376627) failed pushing to NuGet.org: 1ES.PublishNuget@1 could not reach api.nuget.org because 1ES Network Isolation now blocks public feed endpoints by default (the "Stop Network Isolation" step reported api.nuget.org as a blocked connection).
  • Set networkIsolationPolicy: Permissive on the pipeline so the release stage can still push to NuGet.org.

1ES Network Isolation (SFI-ES4.2.4) now blocks public feed endpoints
like api.nuget.org by default, which broke the 1ES.PublishNuget@1
push step during release (build 15376627, "Stop Network Isolation"
step reported api.nuget.org as blocked).

Set networkIsolationPolicy: Permissive on the pipeline so the
publish stage can still reach NuGet.org.

@yury-s Yury Semikhatsky (yury-s) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I doubt it's gonna work

@dgozman
Dmitry Gozman (dgozman) merged commit b633641 into microsoft:main Sep 21, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants