The 60 limit usually indicates that the request is being treated as unauthenticated.

Since the request is being made from GitHub Actions, I would first verify the rate limit independently using the same workflow environment:

- name: Check GitHub API rate limit
  env:
    GH_TOKEN: ${{ github.token }}
  run: |
    gh api rate_limit --jq '.resources.core | {limit, remaining, used, reset}'

Then compare this with the rate limit reported by GoReleaser.

If gh api reports the expected authenticated Actions limit while GoReleaser reports 60, then the issue is likely that GoReleaser is not receiving or using the same token.

Make sure the token is explicitly available to the GoReleaser step, for example:

env:
  GITHUB_TOKEN: ${{ github.token }}

Also verify which environment variable and authentication mechanism the particular GoReleaser version expects.

The important point is that the x-ratelimit-* headers describe the rate limit applied to the specific API request. Therefore, seeing:

x-ratelimit-limit: 60

means that request is currently subject to the 60-request limit; it does not necessarily mean that the GitHub Actions GITHUB_TOKEN itself has a 60-request limit.

I would therefore first confirm that the exact requests made by GoReleaser are authenticated with the Actions token before treating this as a GitHub rate-limit discrepancy.