update-go-version

Update Go Version

Update all Go module files and CI configuration to the latest stable Go release.

Instructions

Phase 0: Discover the latest stable Go version

Fetch the current release list from the official Go downloads API:

https://go.dev/dl/?mode=json

Parse the JSON to find the latest stable release — the entry with "stable": true and the highest version number. Extract the version string (e.g. 1.24.1). Also note the minor-only form (e.g. 1.24) for use in go.mod.

Phase 1: Identify files to update

Find all Go modules and config files in the repo:

find . -name go.mod -not -path '*/vendor/*'
find . -name '.github' -type d
find . -name '*.yml' -path '*/.github/workflows/*'
find . -name '.nvmrc'   # unrelated — skip

Files that typically contain the Go version:

• go.mod — go X.Y directive (use minor version, e.g. go 1.24)
• .github/workflows/*.yml — go-version: fields (use full patch version, e.g. 1.24.1)
• Makefile — GO_VERSION ?= X.Y.Z or similar variables
• Dockerfile / docker-compose.yml — FROM golang:X.Y.Z
• .tool-versions (asdf) — golang X.Y.Z
• toolchain directive in go.mod — toolchain goX.Y.Z

Phase 2: Check current versions

For each go.mod, read the current go directive. If it is already at the latest version, log that fact for this module and continue to the next module (nothing to do for this one).

Phase 3: Update files

For each file identified above, update the Go version string using precise string replacements. Be careful to:

• In go.mod: update only the go directive line (e.g. go 1.23 → go 1.24). Also update the toolchain directive if present (e.g. toolchain go1.23.5 → toolchain go1.24.1).
• In CI YAML: update every go-version: value. Match both quoted and unquoted forms.
• In Makefiles: update version variables only — do not touch logic.
• In Dockerfiles: update the golang: image tag.

Phase 4: Tidy and verify

For each updated go.mod:

1. cd into the module directory.
2. Run go mod tidy to update go.sum for the new toolchain.
3. If a vendor/ directory exists, run go mod vendor.
4. Run go build ./... to confirm nothing broke.
5. Run go test ./... — note any failures and whether they are pre-existing.

Phase 5: Commit

1. Stage go.mod, go.sum, vendor/ (if present), and any updated config files.
2. Commit with a message like:

chore(go): update Go version to X.Y.Z

3. Print a summary of every file changed and the old → new version in each.

Notes

• Always fetch the live version from https://go.dev/dl/?mode=json — do not hard-code a version.
• Use the minor version (1.24) in go.mod and the full patch version (1.24.1) everywhere else, unless the existing file already uses a different precision.
• Do not update go.mod to a version lower than the current one.
• If the repo pins Go via toolchain directive, update both go and toolchain.