chore(deps): update actions/setup-go action to v7

[scality-renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-go	action	major	v6.5.0 → v7.0.0

---

Release Notes

actions/setup-go (actions/setup-go)

v7.0.0

Compare Source

What's Changed

• Migrate to ESM and upgrade dependencies by @​priyagupta108 in #​763
• chore(deps): bump @​actions/cache to 6.2.0 by @​philip-gai in #​771

New Contributors

• @​philip-gai made their first contribution in #​771

Full Changelog: actions/setup-go@v6...v7.0.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[github-actions]

Dependency Bump Evaluation

Version change: actions/setup-go v6.5.0 → v7.0.0 (major)
Semver bump type: major

Changes:

• Internal migration from CommonJS to ECMAScript Modules (ESM)
• Bumped @actions/cache dependency to 6.2.0

Breaking changes: None for consumers. The major version bump is driven by the internal ESM migration, which does not affect the action's public interface. All inputs (go-version, go-version-file, check-latest, token, cache, cache-dependency-path, architecture, go-download-base-url) and outputs (go-version, cache-hit) are identical between v6.5.0 and v7.0.0.

Security concerns: None. Changes come from the official actions/ GitHub org. No new inputs, no behavior changes, no suspicious patterns.

Impact on codebase: The repo uses actions/setup-go in .github/workflows/pre-merge.yaml across 3 jobs (lint, generate, test), all with the same configuration: go-version-file: go.mod. This input is unchanged and fully supported in v7. No impact expected.

CI status: Checks are still in progress at time of evaluation — verify they pass before merging.

Recommendation: SAFE TO MERGE (once CI is green)

Notes: Despite the major version bump, this is a low-risk change. The v6→v7 bump is purely internal (ESM migration + dependency updates) with no changes to the action's public API. PR authored by renovate — not auto-approving per policy.

— Claude Code