Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Nov 6, 2025

Backport of #120696 to release/9.0-staging

/cc @akoeplinger

Customer Impact

  • Customer reported
  • Found internally

no customer impact, this affects our internal builds due to CFS restrictions.

Regression

  • Yes
  • 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.

The api.nuget.org source will clash with the CFSClean network isolation policy
@akoeplinger
Copy link
Member

akoeplinger commented Nov 7, 2025

infrastructure change required to build, servicing-approved

@akoeplinger akoeplinger added the Servicing-approved Approved for servicing release label Nov 7, 2025
@akoeplinger
Copy link
Member

/ba-g failures on macOS are unrelated infrastructure issues

@akoeplinger akoeplinger merged commit 3bb4ae2 into release/9.0-staging Nov 7, 2025
126 of 149 checks passed
@akoeplinger akoeplinger deleted the backport/pr-120696-to-release/9.0-staging branch November 7, 2025 09:15
@github-actions github-actions bot locked and limited conversation to collaborators Dec 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants