From ca6b75508ce2dbabc7de1b825f3bf1be9f17ae9b Mon Sep 17 00:00:00 2001 From: Audiobuzz Date: Thu, 2 Jul 2026 10:07:23 +0000 Subject: [PATCH] ci: pin Go-build step to bash (Gitea runner defaults run steps to sh) The out-of-VM Go build step used `set -euo pipefail`, but the self-hosted Gitea/act runner runs `run:` steps under sh (dash), which rejects `-o pipefail` ("Illegal option"). Add `shell: bash` to the step. Keeping `set -e` is load-bearing: without it a failed go build/test in the first subshell group is masked by the trailing `file` command's success, letting a broken binary reach the Packer build. --- .gitea/workflows/gitea-main-ci.yaml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.gitea/workflows/gitea-main-ci.yaml b/.gitea/workflows/gitea-main-ci.yaml index aa6e96c..37a80d8 100644 --- a/.gitea/workflows/gitea-main-ci.yaml +++ b/.gitea/workflows/gitea-main-ci.yaml @@ -204,6 +204,11 @@ jobs: # Reproducible: pinned Go (1.26.4) + go.sum-pinned deps + -trimpath/no buildid. # fleet-enrol fetches go-tpm from the proxy (pinned by go.sum); hostapi is # stdlib-only (GOPROXY=off). + # shell: bash is explicit — the Gitea/act runner defaults run steps to sh + # (dash), where `set -o pipefail` is an illegal option. `set -e` is + # load-bearing: without it a failed go build/test in the first ( … ) group + # is masked by the trailing `file` success and a broken binary reaches Packer. + shell: bash run: | set -euo pipefail ( cd files/enrol \