-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Install Domains and URLs Update #570
Comments
Thanks @benwells and crew! We appreciate the help. |
This was referenced Dec 27, 2024
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. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
, andv4
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 dotnet/core#9671.
The text was updated successfully, but these errors were encountered: