From 35136cb9adf174f77643fda237925e3f2773775b Mon Sep 17 00:00:00 2001 From: Joshua King Date: Fri, 5 Jun 2026 09:52:14 -0400 Subject: [PATCH] ci: install Go via setup-go (go-react image has Node but not Go) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit build-dev failed with "go: command not found" — the go-react image ships Node but no Go. Restore setup-go (its static Go binary runs on this runner, unlike setup-node's dynamic Node), and keep Node from the image. Co-Authored-By: Claude Opus 4.8 --- .gitea/workflows/build-dev.yaml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/build-dev.yaml b/.gitea/workflows/build-dev.yaml index fa648f1..0884d09 100644 --- a/.gitea/workflows/build-dev.yaml +++ b/.gitea/workflows/build-dev.yaml @@ -16,8 +16,14 @@ jobs: - name: Checkout uses: actions/checkout@v4 - # The go-react image ships Go + Node, so no setup-go/setup-node: - # those download tool-cache binaries that don't run on this runner. + # go-react has Node but not Go. setup-go installs a statically-linked + # Go that runs fine here; setup-node's dynamically-linked Node does + # not (so Node comes from the image instead). + - name: Setup Go + uses: actions/setup-go@v5 + with: + go-version: "1.25" + - name: Toolchain versions run: | go version