Skip to content

ci: upgrade pinned actions/setup-go v6 -> v7 via ratchet - #7

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/github-actions-ratchet-review-b833
Draft

ci: upgrade pinned actions/setup-go v6 -> v7 via ratchet#7
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/github-actions-ratchet-review-b833

Conversation

@cursor

@cursor cursor Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Weekly ratchet maintenance of pinned GitHub Actions.

  • Ran mise run //:ratchet:update (routine, within-@vX-constraint SHA bumps): no changes — every pinned action is already at the latest release within its current major.
  • Checked all 11 pinned actions for newer major versions. The only one behind a major was actions/setup-go (pinned @v6, latest v7.0.0), so it was upgraded with a scoped //:ratchet:upgrade.

What changed

Action Before After Kind
actions/setup-go @v6 924ae3a1 (v6.5.0) @v7 b7ad1dad (v7.0.0) Major upgrade

Only .github/workflows/docker.yml is affected (the sole consumer of setup-go). The pinned SHA and the # ratchet:...@vX constraint comment were both rewritten; no go-version or other inputs changed.

All other pinned actions were verified current and left untouched: actions/checkout@v7, actions/upload-artifact@v7, actions/create-github-app-token@v3, aws-actions/configure-aws-credentials@v6, aws-actions/amazon-ecr-login@v2, docker/metadata-action@v6, docker/setup-qemu-action@v4, docker/setup-buildx-action@v4, docker/build-push-action@v7, jdx/mise-action@v4.

Risk assessment (from changelog)

Overall: low. setup-go v7.0.0 carries no user-facing breaking changes despite the major version.

Per the v6...v7.0.0 changelog, v7.0.0 contains exactly two changes:

  • Migrate to ESM and upgrade dependencies (#763) — internal source/build change to the action itself.
  • Bump @actions/cache to 6.2.0 (#771) — dependency bump.

Breaking-change checks performed:

  • Runtime unchanged: both @v6 and @v7 declare runs.using: node24 in action.yml, so there is no Node runtime jump for the runner.
  • No input/output changes: the go-version: "1.26.0" input we use is unchanged; no inputs were removed or renamed.
  • Supply chain: upgrade performed by ratchet, pinning to the immutable commit SHA b7ad1dad31e06c5925ef5d2fc7ad053ef454303e for v7.0.0 (verified against the upstream tag ref).

The "major" bump is driven by the internal ESM migration and refreshed cache dependency rather than a behavior change, so regression risk to the Docker Build workflow is minimal.

Verification checklist

  • mise install provisions go 1.26, golangci-lint, ratchet 0.11.4
  • mise run //:ratchet:update run first — produced no diff (nothing to bump within existing majors)
  • Confirmed actions/setup-go was the only action with a newer major available
  • Reviewed setup-go v7.0.0 release notes + v6...v7.0.0 commit list
  • Confirmed action.yml runtime is node24 on both v6 and v7 (no runtime break)
  • Confirmed no setup-go inputs/outputs changed; go-version input unaffected
  • mise run //:ratchet:lint passes (all refs remain SHA-pinned with constraint comments)
  • mise run //:ratchet:pin introduces no additional diff beyond the intended change
  • git diff limited to a single line in .github/workflows/docker.yml
  • Pinned SHA b7ad1dad verified to match upstream refs/tags/v7.0.0
  • CI: Go, Docker Build, and Ratchet workflows green on this PR
Open in Web View Automation 

Only major-version bump available this cycle. All other pinned actions
are already at their latest release within existing @vx constraints
(ratchet update produced no diff).

setup-go v7.0.0 changes are internal (source migrated to ESM,
@actions/cache bumped to 6.2.0); runtime stays node24 and no
action inputs/outputs changed, so this is a low-risk upgrade.

Co-authored-by: Nick Pellegrino <nickpell@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant