Skip to content

ci: take the Go version from go.mod (MK8S-516) - #118

Merged
ezekiel-alexrod merged 1 commit into
mainfrom
improvement/MK8S-516-go-version-file
Nov 4, 2026
Merged

ezekiel-alexrod merged 1 commit into
mainfrom
improvement/MK8S-516-go-version-file

Conversation

@ezekiel-alexrod

Copy link
Copy Markdown
Contributor

The pre-merge jobs install Go from GO_VERSION: 1.25, set by hand, while each module declares its Go version in go.mod. When a dependency needs a newer Go, Renovate bumps the go directive and every job fails: #116 (mockery 3.8.1 needs Go 1.26) is red on go.mod requires go >= 1.26.0 (running go 1.25.14). Each job now reads the go.mod of the module it checks.

What changes

Testing

Check Result
actionlint OK, apart from the ubuntu-26.04 label it doesn't know yet
#116 merged on main, with Go 1.26.0 root: build, tests, go generate clean, make build-e2e OK; scenario/: needs go mod tidy (its directive follows the root one), then build and tests OK
not verified: golangci-lint 2.14 on Go 1.26 this PR's CI runs it on Go 1.25, #116's CI will run it on 1.26

Out of scope


Refs: MK8S-516

The pre-merge jobs installed GO_VERSION 1.25, set by hand, while each
module declares its Go version in go.mod. A dependency that needs a
newer Go (mockery 3.8.1 needs 1.26, #116) bumps the go directive and
then fails on every job. Each job now reads the go.mod of the module it
checks.

Refs: MK8S-516
@ezekiel-alexrod
ezekiel-alexrod merged commit d1b98f6 into main Nov 4, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants