Skip to content

Mac release build fails installing .NET 10: setup-dotnet downloads from an origin that now returns 409 #376

Closed

Description

@kellylford

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:

  • https://builds.dotnet.microsoft.com/dotnet/Sdk/10.0.403/dotnet-sdk-10.0.403-osx-arm64.tar.gz: 200
  • https://dotnetorigin.blob.core.windows.net/dotnet/Sdk/10.0.403/dotnet-sdk-10.0.403-osx-arm64.tar.gz: 409

Likely fixes (not tried yet):

  • update actions/setup-dotnet to a release whose install script uses builds.dotnet.microsoft.com;
  • or install .NET on the Mac job with Microsoft's current dotnet-install.sh and set DOTNET_ROOT.

Either way, check GHManage's Mac job, which this setup was copied from. vpk 1.2.161 needs the net10.0 runtime.

Activity

  1. kellylford commented on Oct 25, 2026

    @kellylford
    CollaboratorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions