Failing to download latest go version 1.25.5

Description:
A clear and concise description of what the bug is.

Setup go version spec 1.25.5
Attempting to resolve the latest version from the manifest...
matching 1.25.5...
Failed to resolve version 1.25.5 from manifest
Attempting to download 1.25.5...
matching 1.25.5...
Not found in manifest.  Falling back to download directly from Go
Install from dist
Acquiring go1.25.5 from https://storage.googleapis.com/golang/go1.25.5.linux-amd64.tar.gz
Error: Failed to download version 1.25.5: Error: Unexpected HTTP response: 403

Action version:
Specify the action version
actions/setup-go@v4
Platform:

Ubuntu
macOS
Windows

Runner type:

[ X] Hosted
Self-hosted

Tools version:

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.

Expected behavior:
A description of what you expected to happen.

Actual behavior:
A description of what is actually happening.

Same with 1.24.11

Looks like this is related to actions/go-versions#127

Just a note: The latest https://github.com/actions/setup-go/releases/tag/v6.1.0 release includes a Fall back option to downloading from go.dev/dl instead of storage.googleapis.com/golang

@nicholasngai

This was previously reported in issue #664. PR #667 was created to resolve this for v4.

It is already resolved in v6 as of v6.1.0:

Fall back to downloading from go.dev/dl instead of storage.googleapis.com/golang by @nicholasngai in #665

Yes, Thanks. That worked.

Hello everyone,

Thank you for your report.

The issue is due to the fallback URL (storage.googleapis.com/golang) for downloading Go no longer being available. We have already addressed this in actions/setup-go v6 and are currently working to update the fallback handling in both v4 and v5.

In the meantime, we've released Go versions 1.25.5 and 1.24.11 in the actions/go-versions manifest (PR #128), so your workflow should now be able to resolve and download these versions. Please rerun your workflow to confirm that the issue is resolved.

We will provide further updates as improvements to v4 and v5 are released.

Thank you for your patience!

https://github.com/roshkhatri/valkey-bundle/actions/runs/19912813038/job/57085170640

Run actions/setup-go@v3
Setup go version spec 1.20
Attempting to download 1.20...
matching 1.20...
Not found in manifest.  Falling back to download directly from Go
Install from dist
Acquiring go1.20.14 from https://storage.googleapis.com/golang/go1.20.14.linux-arm64.tar.gz

If you do not set the version explicitly, the action will still default to 1.25.4:

Run actions/setup-go@v6  
  with:  
    go-version: 1.25.x  
    check-latest: false  
    token: ***  
    cache: true  

Setup Go version spec 1.25.x  
Found in cache @ /opt/hostedtoolcache/go/1.25.4/x64  
Added Go to the PATH  
Successfully set up Go version 1.25.x  
/opt/hostedtoolcache/go/1.25.4/x64/bin/go env GOMODCACHE  
/opt/hostedtoolcache/go/1.25.4/x64/bin/go env GOCACHE

If you set check-latest: true, it will find 1.25.5:

Run actions/setup-go@v6  
  with:  
    go-version: 1.25.x  
    check-latest: true  
    token: ***  
    cache: true  

Setup Go version spec 1.25.x  
Attempting to resolve the latest version from the manifest...  
Matching 1.25.x...  
Resolved as '1.25.5'  
Attempting to download 1.25.5...  
Matching 1.25.5...  
Acquiring 1.25.5 from https://github.com/actions/go-versions/releases/download/1.25.5-19880500865/go-1.25.5-linux-x64.tar.gz  
Extracting Go...  
/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/6ea14cef-3621-45cb-9a80-729016e68238 -f /home/runner/work/_temp/cf474942-064b-4e0d-b7a6-d982e32d8595  
Successfully extracted Go to /home/runner/work/_temp/6ea14cef-3621-45cb-9a80-729016e68238

If you set the version to 1.25.5 explicitly, it also finds 1.25.5:

Run actions/setup-go@v6  
  with:  
    go-version: 1.25.5  
    check-latest: false  
    token: ***  
    cache: true  

Setup Go version spec 1.25.5  
Attempting to download 1.25.5...  
Matching 1.25.5...  
Acquiring 1.25.5 from https://github.com/actions/go-versions/releases/download/1.25.5-19880500865/go-1.25.5-linux-x64.tar.gz  
Extracting Go...  
/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/54ebe2c2-ad36-434a-8bf8-1ebf4d0f48d4 -f /home/runner/work/_temp/1d8dd37e-aa75-4f2d-8876-30633ebb5044  
Successfully extracted Go to /home/runner/work/_temp/54ebe2c2-ad36-434a-8bf8-1ebf4d0f48d4

This was previously reported in issue #664. PR #667 was created to resolve this for v4.

It is already resolved in v6 as of v6.1.0:

Fall back to downloading from go.dev/dl instead of storage.googleapis.com/golang by @nicholasngai in #665

I meant to quote this, since it mentions being fixed in v6, I realise this issue is about v4

Hello,
I also have the same kind of issue using v5

Run actions/setup-go@v5
Setup go version spec 1.17
Attempting to download 1.17...
matching 1.17...
Not found in manifest.  Falling back to download directly from Go
Install from dist
Acquiring go1.17.13 from https://storage.googleapis.com/golang/go1.17.13.linux-arm64.tar.gz
Error: Failed to download version 1.17: Error: Unexpected HTTP response: 403

From what I read, a fix for v5 is coming soon. Are there any updates as to when it will be released? Thank you!

@HarithaVattikuti @priyagupta108 Could we close this as dupe of #664? And maybe re-open #664 until we have fixes picked into all the previous versions?

Can confirm the following fixes this issue:

      - uses: actions/setup-go@v6
        with:
          check-latest: true
          go-version: '1.25'

Saw the same in v5 for 1.18.x. While I'm glad a v5 port is going to happen, for a simple/naive Go workflow, e.g. just calling something like go test ./... then changing v5 to v6 works well enough. Tests are now passing. Thanks for the info in this thread.

Hello everyone,

We’re happy to share that updates have now been released for both actions/setup-go v4 and v5 to address fallback handling for downloading Go versions. With these updates, Go versions should now reliably resolve and download as expected in your workflows.

As this issue has been resolved, we will proceed to close it. If you encounter any further issues, please feel free to reach out to us.

Thank you all for your patience and feedback!