deps: upgrade go version to go1.26 - #2782
Conversation
Bump the go directive in all six modules (root and the five hack modules),
the devcontainer Go tarball and the hack builder base images from 1.25 to
1.26.7. The devcontainer was pinned to go1.25.1 while go.mod required
1.25.8, so GOTOOLCHAIN had to download a matching toolchain on every
build; it now matches go.mod.
Running go mod tidy on the hack modules also refreshed their indirect
dependencies: golang.org/x/{crypto,net,text}, google.golang.org/api,
cloud.google.com/go/auth and enterprise-certificate-proxy.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Upgrades all Go modules and development/build environments to Go 1.26.7.
Changes:
- Updated six module directives and four builder images.
- Aligned the devcontainer toolchain.
- Refreshed affected indirect dependencies and checksums.
Reviewed changes
Copilot reviewed 11 out of 15 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
go.mod |
Updates the root Go version. |
.github/.devcontainer/Dockerfile |
Installs Go 1.26.7. |
hack/create-e2e-accounts/go.mod |
Updates Go and indirect dependencies. |
hack/create-e2e-accounts/go.sum |
Refreshes dependency checksums. |
hack/create-e2e-accounts/Dockerfile |
Updates the builder image. |
hack/delete-e2e-data-mysql/go.mod |
Updates the Go version. |
hack/delete-e2e-data-mysql/Dockerfile |
Updates the builder image. |
hack/delete-e2e-data-postgres/go.mod |
Updates Go and indirect dependencies. |
hack/delete-e2e-data-postgres/go.sum |
Refreshes dependency checksums. |
hack/delete-e2e-data-postgres/Dockerfile |
Updates the builder image. |
hack/delete-postgres-data-warehouse/go.mod |
Updates Go and indirect dependencies. |
hack/delete-postgres-data-warehouse/go.sum |
Refreshes dependency checksums. |
hack/delete-postgres-data-warehouse/Dockerfile |
Updates the builder image. |
hack/delete-redis-retry-keys/go.mod |
Updates Go and indirect dependencies. |
hack/delete-redis-retry-keys/go.sum |
Refreshes dependency checksums. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
go1.26 vet reports copylocks for the sync.Map test fixtures. Use plain maps for the existing/expected cache and populate the service's sync.Map directly instead of assigning a copy. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
I am addressing errors that occurred in the following file when running the |
|
To check for any missed corrections, I performed a grep search on the pre-update version (1.25) and found no missed corrections. |
|
I reviewed the release notes and performed a grep search on libraries with specification changes to verify their usage. I assessed the potential impact on each library in use and confirmed that there are no adverse effects. ・net/url: No impact |
Follows #2097
Fixes #2474
What this PR does
Bumps the Go toolchain from 1.25 to 1.26.7 in every place the version is pinned: the
godirective in all six modules (root plus the fivehackmodules), the devcontainer's Go tarball, and thegolangbuilder base images used by thehackDockerfiles.Background / Why this PR is needed
Keeps the project on a current Go release, following the same steps as the 1.25 upgrade in #2097. No CI changes are needed because every workflow resolves the version through
go-version-file.The devcontainer had also drifted from
go.mod: it installed go1.25.1 whilego.modrequired 1.25.8, so under the defaultGOTOOLCHAIN=autothe toolchain baked into the image was never the one actually used — Go downloaded 1.25.8 on demand instead. Both are now 1.26.7.Points
go mod tidyon thehackmodules also refreshed their indirect dependencies (golang.org/x/{crypto,net,text},google.golang.org/api,cloud.google.com/go/auth,enterprise-certificate-proxy). The root module's dependencies are untouched — only itsgodirective moved.hackDockerfiles is intentionally left as it was.create-e2e-accountsstays patch-pinned (golang:1.26.7) because CI builds and publishes that image on every change under its directory, while the other three stay minor-pinned (golang:1.26) as they are only built by hand from their local Makefiles. Aligning them is out of scope here..protofiles and no Go interfaces, so no generated files should change.