[Bug]: Manifests using azureedge.net subdomain(s) might have to be updated to using different domain

[o-l-a-v]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues/PRs to ensure it has not already been reported or fixed.
• I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

All using azureedge.net

Expected/Current Behaviour

Due to Edgio (CDN) being bankrupt, it seems that all azureedge.net subdomains will stop working as early as January 2025.

• https://learn.microsoft.com/en-us/azure/cdn/edgio-retirement-faq
• 2024-12-24: Critical: .NET install domains and URLs are changing dotnet/core#9671
• 2024-12-26: https://devblogs.microsoft.com/dotnet/critical-dotnet-install-links-are-changing/
• 2024-12-30: https://www.bleepingcomputer.com/news/microsoft/microsoft-issues-urgent-dev-warning-to-update-net-installer-link/
• 2024-12-31: dotnet CDN tracking issue dotnet/core#9674

I've already updated one manifest ( #6424 ), but it might have to be done with all manifests using azureedge.net? 🤔

As per the linked GitHub issue, there will be an update on 2nd of January 2025. Maybe one should wait for that announcement before doing anything more.

Relevant issues:

• winget-pkgs: [Update Request]: Microsoft.Dotnet.* (update CDN urls) microsoft/winget-pkgs#202037

Steps to Reproduce

Not relevant

Possible Solution

Replace "azureedge.net" in all affected manifests

Scoop and Buckets Version

Not relevant

Scoop Config

Not relevant

PowerShell Version

Not relevant

Additional Softwares

No response

[niheaven]

#6424