[v5] Fall back to downloading from go.dev/dl instead of storage.googleapis.com/golang

[nicholasngai]

Description:

Cherry-picking #665 onto v5.

Related issue:

Closes #664.

Check list:

• Mark if documentation changes are required.
• Mark if tests were added or updated to cover the changes.

[aparnajyothi-y]

Hello @nicholasngai, Thanks for this pull request. Could you also include the audit-related fixes as part of this change, just for the releases/v5 branch to move forward.

[nicholasngai]

Hi @aparnajyothi-y! What audit-related fixes are you referring to?

[nicholasngai]

@aparnajyothi-y Hey, just bumping this question. :)

[rolandshoemaker]

@nicholasngai I believe @aparnajyothi-y is referring to https://github.com/actions/setup-go/actions/runs/18602396198/job/53580106842?pr=666, some npm packages need to be updated to resolve security issues.

[aparnajyothi-y]

Hi @nicholasngai, apologies for the delay and thank you for following up. Yes, as @rolandshoemaker pointed out, I was referring to the security audit fixes needed for the releases/v5 branch by running npm audit fix command. specifically updating the npm packages flagged in the audit report to ensure we resolve the security warnings. It would be great if we could include those updates along with this change so the v5 branch stays compliant.
Let me know if you need any details and thanks again for your contribution!

[nicholasngai]

@aparnajyothi-y Sorry for the delay here! I ran npm audit fix on all the branches. Do you mind helping me getting them all merged in? Thanks!

• [v5] Fall back to downloading from go.dev/dl instead of storage.googleapis.com/golang #666
• [v4] Fall back to downloading from go.dev/dl instead of storage.googleapis.com/golang #667
• [v3] Fall back to downloading from go.dev/dl instead of storage.googleapis.com/golang #668

[aparnajyothi-y]

Hi @nicholasngai , the checks are still failing, but given the community interest and the broader value of this update, we’re moving forward with incorporating these changes so that the v5 branch remains fully compliant for release.

Please let me know if you need any additional details. Thanks again for your contribution and really appreciate the effort!