Skip to content

SCHED-2200: Migrate to Go 1.26#2789

Open
theyoprst wants to merge 1 commit into
SCHED-2200/00from
SCHED-2200/0
Open

SCHED-2200: Migrate to Go 1.26#2789
theyoprst wants to merge 1 commit into
SCHED-2200/00from
SCHED-2200/0

Conversation

@theyoprst

@theyoprst theyoprst commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

Problem

Go 1.26 has been out since February 2026 and the project is still on 1.25. The k8s 1.36 library stack (next PR in this stack) requires Go 1.26, so the toolchain moves first, separately, to keep runtime behavior changes (new default GC) attributable.

Stacked on #2788: lint runs on pull_request_target with workflow definitions from the default branch, so lint here stays red until #2788 merges to main. Rebase the stack after that merge to re-trigger checks.

Solution

  • go 1.26.0 directive, golang:1.26 base images
  • gomodguard -> gomodguard_v2 in the linter config
  • golang.org/x/exp becomes indirect, mockery output picks up go1.26 formatting

Testing

go build, full unit suite, make lint, make sync-version-from-scratch UNSTABLE=false with no drift.

Release Notes

Feature: soperator binaries are built with Go 1.26.

Bump the go directive to 1.26.0 and golang base images to 1.26. Switch gomodguard to gomodguard_v2 in the linter config. golang.org/x/exp becomes an indirect dependency and mockery output picks up go1.26 formatting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

go Pull requests that update Go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant