Skip to content

[Chore] Upgrade Go toolchain to 1.26.4 - #662

Merged
jamieplu merged 2 commits into
meshery-extensions:masterfrom
rishiraj38:chore/upgrade-go-1.26.4
Jun 9, 2026
Merged

jamieplu merged 2 commits into
meshery-extensions:masterfrom
rishiraj38:chore/upgrade-go-1.26.4

Conversation

@rishiraj38

Copy link
Copy Markdown
Contributor

Description

Upgrade Go toolchain from 1.23 to 1.26.4 to pick up the latest security and bug fixes.

Changes

  • go.mod: go 1.23 + toolchain go1.24.1 → go 1.26.4 (toolchain directive removed)
  • Dockerfile: golang:1.23 → golang:1.26
  • build/Makefile.core.mk: GOVERSION = 1.23 → 1.26
  • CI workflows: go-version: 1.23 → 1.26 in ci.yml, build-and-release.yml, update-oam-defs.yml, error-ref-publisher.yaml

Verification

  • ✅ go build ./...
  • ✅ go test ./...
  • ✅ go vet ./...

Compatibility Checks

  • url.ParseRequestURI in linkerd/addons.go — safe, not affected by Go 1.26 net/url.Parse host-colon change
  • No httputil.ReverseProxy.Director or crypto/rsa PKCS#1 v1.5 usage
  • golangci-lint v2.12.1 (built with go1.26.2) confirms Go 1.26 support

Relates to meshery/meshery#19875

Update go.mod, Dockerfile, Makefile, and CI workflows to use Go 1.26.4.
Remove toolchain directive (go 1.26.4 is specific enough).

Verified: go build, go vet, go test all pass.

Relates to meshery/meshery#19875

Signed-off-by: Rishi Raj <[email protected]>
@jamieplu
jamieplu merged commit 2fdf1b5 into meshery-extensions:master Jun 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants