Skip to content

ci: test against per-module minimum go version#215

Draft
thaJeztah wants to merge 1 commit into
moby:mainfrom
thaJeztah:go_matrix
Draft

ci: test against per-module minimum go version#215
thaJeztah wants to merge 1 commit into
moby:mainfrom
thaJeztah:go_matrix

Conversation

@thaJeztah
Copy link
Copy Markdown
Member

Go-setup action allow specifying both a "go-version" and "go-version-file", in which case it falls back to the version-file if "go-version" is empty.

This allows us to iterate over all modules, and run CI on the oldest supported Go version for each (in addition to "oldstable" and "stable").

Go-setup action allow specifying both a "go-version" and "go-version-file",
in which case it falls back to the version-file if "go-version" is empty.

This allows us to iterate over all modules, and run CI on the oldest
supported Go version for each (in addition to "oldstable" and "stable").

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah thaJeztah requested a review from kolyshkin March 26, 2026 23:28
timeout-minutes: 10 # guardrails timeout for the whole job

env:
GOTOOLCHAIN: local
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Is this a request for go to NOT download another go version? If yes, why do we need it here? I mean, it may only happen if we have go.mod with go version less than specified here, which should never be the case.

Or is this something more generic, like "don't download anything" and omitting it may mask some issue?

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.

2 participants