From aed83268a0ae419b6def99375cf6bb94410da690 Mon Sep 17 00:00:00 2001 From: bsodfather Date: Sun, 25 Oct 2026 11:37:27 +0000 Subject: [PATCH] fix(release): publish assets to the public HTTPS Gitea origin The release job container sees gitea.server_url as the internal http://gitea:3000 origin, so scripts/ci-release-assets.py refused to forward its token (run 865 failed at the publish step after packaging). Point the publisher at https://git.itexp.me, the origin the repository already uses for the public URL. --- .gitea/workflows/release.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/release.yml b/.gitea/workflows/release.yml index b28407c..7723349 100644 --- a/.gitea/workflows/release.yml +++ b/.gitea/workflows/release.yml @@ -212,7 +212,9 @@ jobs: - name: Publish release bundles, checksums, evidence, and SBOM to Gitea if: startsWith(gitea.ref, 'refs/tags/v') env: - GITEA_SERVER_URL: ${{ gitea.server_url }} + # gitea.server_url inside the job container is the internal http://gitea:3000 origin; + # the publisher only forwards its token to the public HTTPS origin. + GITEA_SERVER_URL: https://git.itexp.me GITEA_REPOSITORY: ${{ gitea.repository }} GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }} RELEASE_TAG: ${{ gitea.ref_name }}