You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mac release build fails installing .NET 10: setup-dotnet downloads from an origin that now returns 409 #376
The macOS job of "Release The Chat Place" has failed since at least 2026-10-25 at actions/setup-dotnet (dotnet-version: '10.0.x'), before any of our build runs. So the next release's Mac build will fail the same way.
dotnet-install: Download attempt #2 has failed: 409 Unable to download https://dotnetorigin.blob.core.windows.net/dotnet/Sdk/10.0.403/dotnet-sdk-10.0.403-osx-arm64.tar.gz. Returned HTTP status code: 409.
##[error]Failed to install dotnet, exit code: 1. ... Could not find `.NET Core SDK` with version = 10.0.403
Seen on PR #371 (run 40224290297) and PR #375 (run 40226831541, and again on re-run). The Windows job passes.
What I checked: the same SDK downloads fine from Microsoft's current server. Only the old origin refuses it:
Not ours, and fixed upstream. The 409 came from a broken .NET release on 2026-10-25 (dotnet/core#10660; reported as actions/setup-dotnet#794, closed the same day as fixed). We were already on setup-dotnet v6.0.0, its latest release, so there was nothing to upgrade.
Since the fix, the macOS job has passed twice, with actions/setup-dotnet and Install vpk both succeeding (runs 40233351233 and 40234330475 on #377). No workflow change needed; the next release's Mac build should be fine. If it comes back, the fallback is Microsoft's current dotnet-install.sh with DOTNET_ROOT set, as the issue suggested.
Activity
kellylford commentedon Oct 25, 2026
Not ours, and fixed upstream. The 409 came from a broken .NET release on 2026-10-25 (dotnet/core#10660; reported as actions/setup-dotnet#794, closed the same day as fixed). We were already on setup-dotnet v6.0.0, its latest release, so there was nothing to upgrade.
Since the fix, the macOS job has passed twice, with
actions/setup-dotnetandInstall vpkboth succeeding (runs 40233351233 and 40234330475 on #377). No workflow change needed; the next release's Mac build should be fine. If it comes back, the fallback is Microsoft's currentdotnet-install.shwithDOTNET_ROOTset, as the issue suggested.