From 957f5701d49eeb176cfe624d5cc76c96552c1379 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 17 Jul 2026 23:47:25 -0500 Subject: [PATCH] chore(org): retarget release workflow to RunicGateway/link Repo was transferred UOM -> RunicGateway. The REPO env var drives both the git push URL (bump commit + tag) and the release API base, so the release workflow would otherwise still target the old UOM/link path. --- .gitea/workflows/release.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/release.yml b/.gitea/workflows/release.yml index 6dc9d5f..b59d401 100644 --- a/.gitea/workflows/release.yml +++ b/.gitea/workflows/release.yml @@ -22,7 +22,7 @@ # nothing releasable -> no release is cut # (first ever run, no tag) -> releases the current Cargo.toml version as-is # -# Prerequisites (Settings → Actions → Secrets on UOM/link): +# Prerequisites (Settings → Actions → Secrets on RunicGateway/link): # REGISTRY_USER — Gitea username the token below belongs to # REGISTRY_TOKEN — Gitea access token. For image builds it needed # write:package; THIS workflow additionally needs @@ -46,7 +46,7 @@ concurrency: env: GITEA_HOST: gitea.whitlocktech.com - REPO: UOM/link + REPO: RunicGateway/link WORKDIR: sidecar BIN: uo-link-sidecar LINUX_TARGET: x86_64-unknown-linux-gnu -- 2.49.1