From fd0aff6424d768edcaf0edf175c0ea26e200a980 Mon Sep 17 00:00:00 2001 From: JOY <5027251+JOY@users.noreply.github.com> Date: Thu, 16 Jul 2026 21:48:36 +0700 Subject: [PATCH] fix(ci): pin gh release commands to fork via GH_REPO Since the job adds a git remote named 'upstream' (blockscout/frontend), gh CLI resolves it as the default repo and 'gh release create/delete' target the upstream repo, failing with HTTP 403. Releases have been silently missing since v2.8.1. Set GH_REPO to pin gh to the fork. Co-Authored-By: Claude Fable 5 --- .github/workflows/sync-upstream.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/sync-upstream.yml b/.github/workflows/sync-upstream.yml index ed7d5106e6..2deda0f399 100644 --- a/.github/workflows/sync-upstream.yml +++ b/.github/workflows/sync-upstream.yml @@ -101,6 +101,11 @@ jobs: if: steps.target.outputs.skip == 'false' && steps.merge.outputs.result == 'success' env: GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} + # Pin gh to this fork. Without this, gh resolves the default repo + # from git remotes and prefers the one named "upstream" + # (blockscout/frontend, added earlier in this job), so release + # create/delete hits the upstream repo and fails with HTTP 403. + GH_REPO: ${{ github.repository }} run: | TAG="${{ steps.target.outputs.tag }}" # Delete existing release if any (from upstream fork sync)