Repository navigation
ci: pin the .NET 10 SDK to 10.0.402 (#461, 10.x) - #462
Merged
Merged
Conversation
…hat answers 409 (#461) Resolving "latest 10.0" from global.json goes through an aka.ms link that now redirects to dotnetorigin.blob.core.windows.net, which answers 409 for every version. An exact version downloads from builds.dotnet.microsoft.com. global.json is unchanged, so local builds are not affected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #461
Problem
Since about 19:00 UTC, every job on a PR into
release/10.xfails at "Setup .NET".global.jsonasks for10.0.100withlatestFeature, soactions/setup-dotnetresolves "latest 10.0" through an aka.ms link, and that link now redirects todotnetorigin.blob.core.windows.net, which answers HTTP 409 for every version, 10.0.402 included. It blocks #454, #458, #459 and #460, and thev10.3.0tag'srelease.ymlwould fail the same way.Change
The four
Setup .NETsteps indotnet.ymland the two inrelease.ymlask fordotnet-version: 10.0.402. With an exact version, the install script downloads from its primary link onbuilds.dotnet.microsoft.com, which answers 200. That's howmain's exact RC2 pin keeps working. 10.0.402 is the SDK the last greenrelease/10.xrun used.global.jsonis unchanged, so local builds aren't affected. Remove the pin once aka.ms resolves to a working host again (#461 says so).main's docs jobBuild (10.x)gets the same pin in its own PR.Tests
This PR's own CI is the check: it runs the changed workflow, so its "Setup .NET" steps install 10.0.402 and the jobs then run as before.
release.ymlonly runs on a tag, so it's checked atv10.3.0.🤖 Generated with Claude Code