Cache key incorrectly uses 'x64' instead of '386' when architecture is set to '386' on Windows

[ryo-kagawa]

Description:
When using architecture: '386' on a Windows runner, the cache key is incorrectly generated with the x64 suffix (e.g., setup-go-Windows-x64-go-1.22.12-${hash}). This prevents proper cache isolation between different architectures.

Action version:
v6.4.0

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:

• 1.22.12
• 1.23.12
• 1.24.13
• 1.25.8
• 1.26.1

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

    runs-on: windows-2025
    steps:
      - uses: actions/checkout@v6
      - uses: actions/setup-go@v6
        with:
          architecture: '386'

https://github.com/ryo-kagawa/go-utils/actions/runs/24959462267/job/73083475812

Expected behavior:
setup-go-Windows-386-go-1.22.12-${hash}

Actual behavior:
setup-go-Windows-x64-go-1.22.12-${hash}

[priya-kinthali]

Hello @ryo-kagawa👋,
Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.

[priya-kinthali]

Hello @ryo-kagawa👋,
We have investigated it and would like to inform you that, as per the current design, cache key generation relies on the runner’s host architecture to ensure consistency across builds, which is primarily why such an error is observed.

However, cache key creation based on user specified architecture input would require extending and updating the existing cache key logic, which constitutes as a feature request rather than a bug. Hence, we will re-classify this as a feature request to better reflect the nature of the change.

Once again, Thank you for bringing this to our attention.