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.
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user