From 3d3b00c71bf63175e43a8c78123fdc77f11319f1 Mon Sep 17 00:00:00 2001 From: Simone Date: Sun, 17 May 2026 21:08:49 +0200 Subject: [PATCH] fix(ci): harden release job condition (avoid stuck 'blocked') A bare `if: github.ref_type == 'tag'` on a needs-dependent job can leave `release` stuck in "blocked" instead of skipped for workflow_dispatch runs on Gitea. Use the explicit ${{ github.event_name == 'push' && github.ref_type == 'tag' }} form. Co-Authored-By: Claude Opus 4.7 --- .gitea/workflows/build-ns7zip.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/build-ns7zip.yml b/.gitea/workflows/build-ns7zip.yml index 91e1113..1b40648 100644 --- a/.gitea/workflows/build-ns7zip.yml +++ b/.gitea/workflows/build-ns7zip.yml @@ -55,7 +55,10 @@ jobs: # Requires a GITEA_TOKEN secret with repo write permissions. release: needs: build - if: github.ref_type == 'tag' + # Tag pushes only. Explicit ${{ }} + event gate: a bare + # `if: github.ref_type == 'tag'` can leave the job stuck "blocked" + # (instead of skipped) on Gitea for workflow_dispatch runs. + if: ${{ github.event_name == 'push' && github.ref_type == 'tag' }} runs-on: windows-build steps: