From a33987dac506ce1f7528ca6e6806fce2cb37d63b Mon Sep 17 00:00:00 2001 From: Ayoub Mrini Date: Tue, 25 Aug 2026 20:05:54 +0200 Subject: [PATCH] chore(merge-flow): use go-version stable instead of pinning to go.mod go.mod declares a minimum Go version, but workspace sub-modules or their deps may require a newer patch. Upstream CI typically runs a newer Go (e.g. 1.27) hiding such inconsistencies, so pinning to go.mod can break "go mod tidy + vendor" here with errors like "module X requires go >= 1.25.10 (running go 1.25.8)". Use go-version: stable and let downstream repos CIs decide whether they are ready. Ref: https://github.com/rhobs/syncbot/actions/runs/32792332062/job/97636246281 --- .github/workflows/merge-flow.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/merge-flow.yaml b/.github/workflows/merge-flow.yaml index 75c5b97..e20b6db 100644 --- a/.github/workflows/merge-flow.yaml +++ b/.github/workflows/merge-flow.yaml @@ -197,7 +197,11 @@ jobs: git diff --cached --exit-code || git commit -s -m "[bot] add VERSION file with ${version_from_tag}" - uses: actions/setup-go@b7ad1dad31e06c5925ef5d2fc7ad053ef454303e # v7 with: - go-version-file: go.mod + # Don't pin to go.mod: deps may require a newer Go + # patch, and upstream CI may already be running it, hiding + # errors like "module X requires go >= 1.25.10 (running go 1.25.8)". + # Use stable and let downstream repos' CIs decide whether they are ready. + go-version: stable # Install NodeJS + pnpm to build frontend assets. - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7 with: