Skip to content

chore(go): weekly Go toolchain upgrade - #469

Open
localstack-bot wants to merge 2 commits into
mainfrom
chore/weekly-go-upgrade
Open

localstack-bot wants to merge 2 commits into
mainfrom
chore/weekly-go-upgrade

Conversation

@localstack-bot

Copy link
Copy Markdown
Collaborator

Automated weekly Go toolchain upgrade.

  • Updates the toolchain directive to the latest released Go version.
  • Runs go mod tidy to keep module files consistent.

@localstack-bot localstack-bot added the dependencies Pull requests that update a dependency file label Aug 24, 2026
@localstack-bot
localstack-bot requested a review from a team as a code owner August 24, 2026 08:12
@localstack-bot localstack-bot added docs: skip Pull request does not require documentation changes semver: patch labels Aug 24, 2026

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the automated weekly Go toolchain bump (go1.26.6 → go1.27.0) in both go.mod files; the change itself is minimal and consistent, but it currently reddens CI.

  1. issue(blocking): The Lint job fails on this head — golangci-lint v2.9.0 (pinned in .tool-versions, built with go1.26) refuses to run against the now-targeted go1.27.0: can't load config: the Go language version (go1.26) used to build golangci-lint is lower than the targeted Go version (1.27.0). The toolchain bump needs a matching golangci-lint bump in .tool-versions (to a release built with Go ≥1.27) in the same PR before this can merge.
  2. thought: This breakage recurs whenever Go's toolchain outpaces the pinned linter — consider having weekly-go-upgrade.yml also bump golangci-lint to latest in the generated PR so the linter and toolchain stay in lockstep.

Automated review on behalf of @gtsiolis.


Generated by Claude Code

@localstack-bot
localstack-bot force-pushed the chore/weekly-go-upgrade branch from 0b0996f to cce64bb Compare August 31, 2026 08:04

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-review of the re-pushed weekly toolchain bump (go1.26.6 → go1.27.0); the change is still minimal and consistent, but the blocking lint breakage I flagged before is unresolved on this new commit.

  1. issue(blocking): .tool-versions still pins golangci-lint 2.9.0 (built with go1.26), so the Lint job stays red on this head while every other job is green — I confirmed via the check-runs API that Lint failed with golangci-lint exit code 3 (config load). Bump golangci-lint to a release built with Go ≥1.27 in this same PR so the linter can target go1.27.0.
  2. thought(non-blocking): as noted last time, having weekly-go-upgrade.yml also bump golangci-lint to latest in the generated PR would keep linter and toolchain in lockstep and stop this recurring weekly.

Automated review on behalf of @gtsiolis.


Generated by Claude Code

@localstack-bot
localstack-bot force-pushed the chore/weekly-go-upgrade branch 2 times, most recently from 2bb407b to 8065c80 Compare September 14, 2026 08:04
golangci-lint 2.9.0 was built with Go 1.26 and refuses to lint a
module targeting Go 1.27, which the weekly toolchain bump now does.
Also fixes the new staticcheck QF1012 findings it surfaces.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file docs: skip Pull request does not require documentation changes semver: patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants