.NET Install Domains and URLs Update

[benwells]

Some .NET binaries and installers currently hosted on Azure Content Delivery Network (CDN) domains ending in .azureedge.net will move to new domains as the provider, edg.io, will soon cease operations. There may be downtime or unavailability of .azureedge.net domains in the future as the .NET team is required to migrate to a new CDN and set of domains moving forward.

This week, we will be releasing updates for the v1, v2, v3, and v4 major setup-dotnet tags to address this change. Workflows pinned to these version tags should not experience breaking changes.

If your workflows are pinned to specific SHAs or minor tags, please upgrade to a major release tag to avoid service disruptions. Edgio has confirmed their services will be operational until at least January 15, 2025.

For updates, follow https://github.com/dotnet/core/issues/9671.

[richlander]

Thanks @benwells and crew! We appreciate the help.

[ben-wilson-mews]

https://github.com/actions/setup-dotnet/pull/566 https://github.com/actions/setup-dotnet/pull/567 https://github.com/actions/setup-dotnet/pull/568 https://github.com/actions/setup-dotnet/pull/569

For anyone doing due diligence. 566 has been opened by github staff to fix the issue, it includes a fallback url using the original (concerning), this was done for v4. Community members have replicated it for v3, v2, v1 tags in much a similar way.

[richlander]

it includes a fallback url using the original (concerning)

I created a tracking issue for when we plan to remove the old domain for the official install script. GitHub folks can use that for their decision making.

https://github.com/dotnet/install-scripts/issues/559

[aparnajyothi-y]

Hello Everyone, This issue has been addressed across multiple versions of the setup-dotnet. Below are the details for the corresponding PRs:

• V4: Fallback logic and update install scripts were implemented to the V4 in PR #572, which resolves the issue for this version.
• V3: Fallback logic and update install scripts were implemented to the V3 in PR #573, ensuring compatibility with v3.
• V2: Fallback logic and update install scripts were implemented to the V2 in PR #576 for v2.
• V1: Fallback logic and update install scripts were implemented to the V1 version in PR #577.

The update has been completed in setup-dotnet, so we are closing this issue.