Automate Go version updates via scheduled workflow

[Copilot]

Manual Go version updates require tracking releases and updating multiple files with different version format requirements. This workflow automates the process.

Implementation

Workflow: .github/workflows/go-version-update.yml

• Queries go.dev/dl/?mode=json for latest release
• Compares against MODULE.bazel version (full version including patch number)
• Updates on version mismatch:
  • MODULE.bazel → go_sdk.download(version = "1.26.0")
  • go/extractor/go.mod → go 1.26 and toolchain go1.26.0
  • go/extractor/autobuilder/build-environment.go → maxGoVersion = "1.26"
  • go/actions/test/action.yml → default: "~1.26.0"
• Creates/updates PR on workflow/go-version-update branch
• Schedule: Weekly on Mondays at 3 AM UTC

Excluded from automation:

• go/ql/** - Query-specific code requiring manual review
• docs/** - Documentation requiring manual updates

Technical Details

• Uses sed -E for cross-platform regex compatibility (GNU/BSD)
• Escapes version strings for safe regex patterns
• Validates API responses and version extraction
• Deduplicates PRs via branch check
• Fails fast on malformed data
• Compares full semantic versions including patch numbers (e.g., 1.26.0 vs 1.26.4)

Example

When Go 1.27.0 releases:

Current: 1.26.0 → Latest: 1.27.0
Updates 4 files → Commits to workflow/go-version-update → Creates PR "Go: Update to 1.27.0"

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[owen-mc]

@copilot This only looks at major.minor, but actually we really care about the patch number as well. Please update it. Note that LATEST_GO_VERSION is in the format "go1.26.4" and CURRENT_VERSION is in the format "1.26.0". You could strip the "go" prefix from the first one before you compare them, for example.

[Copilot]

@copilot This only looks at major.minor, but actually we really care about the patch number as well. Please update it. Note that LATEST_GO_VERSION is in the format "go1.26.4" and CURRENT_VERSION i...

Updated the workflow to use full version numbers (including patch) in commit messages, PR title, and PR body. The version comparison was already correctly comparing full versions including patch numbers (line 76), but the messages were only showing major.minor. Fixed in commit ef29d22.

[Copilot]

Pull request overview

This PR adds a scheduled GitHub Actions workflow to automatically detect the latest Go release and, when it differs from the repo’s pinned version, update the relevant version pins and open/update a PR on a dedicated branch.

Changes:

• Introduces a weekly + manual-trigger workflow to fetch the latest Go version from go.dev/dl/?mode=json and compare it to MODULE.bazel.
• Automatically edits the Go version in MODULE.bazel, go/extractor/go.mod, go/extractor/autobuilder/build-environment.go, and go/actions/test/action.yml.
• Creates or updates a PR from workflow/go-version-update with the changes.

Show a summary per file

File	Description
.github/workflows/go-version-update.yml	Adds the automation that fetches Go versions, applies updates across multiple files, and opens/updates a PR on a scheduled cadence.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 4

[owen-mc]

I did a trial run here and it produced this PR, which seemed correct. I have made a few small tweaks since then, but nothing that requires re-running the trial, I think.