From 86325ae0bd8267608b81a0f629d10bb6635089e5 Mon Sep 17 00:00:00 2001
From: Vishal Rana <v@labstack.com>
Date: Wed, 21 Oct 2026 19:53:44 -0700
Subject: [PATCH] ci(release): build binaries with the Go version from go.mod

The binary job pinned Go 1.27.2 in a workflow variable while go.mod moved
to 1.27.3 in #368. With GOTOOLCHAIN=local every binary build stopped with
"go.mod requires go >= 1.27.3", so v2026.10.21-alpha published its images
but no archives or GitHub Release. Read the version from go.mod, as every
other workflow job already does, so the release cannot drift again.
---
 .github/workflows/release.yml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 9b426e5f..5341b303 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -13,7 +13,6 @@ permissions:
   contents: read
 
 env:
-  GO_VERSION: "1.27.2"
   IMAGE: ghcr.io/labstack/fanout
   DOCKERHUB_IMAGE: docker.io/labstack/fanout
   MCP_PUBLISHER_VERSION: "1.8.1"
@@ -96,7 +95,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
       - uses: actions/setup-go@b7ad1dad31e06c5925ef5d2fc7ad053ef454303e # v7.0.0
         with:
-          go-version: ${{ env.GO_VERSION }}
+          go-version-file: go.mod
       - name: Build
         env:
           CGO_ENABLED: "1"