release: name the image by the public registry host, not the internal server url
Gates / frontend (push) Successful in 45s
Gates / package (push) Successful in 3m52s
Gates / container (push) Successful in 2m18s
CI / gates (push) Successful in 12m35s
Gates / test-aarch64 (push) Successful in 4m26s
Gates / frontend (push) Successful in 47s
Release / guard (push) Successful in 1m16s
Gates / test (push) Successful in 1m9s
Gates / package (push) Successful in 31s
Gates / container (push) Successful in 34s
Release / gates (push) Successful in 7m29s
Release / publish (push) Successful in 5m15s
Gates / test (push) Successful in 1m11s
Gates / test-aarch64 (push) Successful in 4m28s

This commit is contained in:
2026-08-08 21:14:37 +02:00
parent 266dde7396
commit 51d8281abb
2 changed files with 19 additions and 1 deletions
+7
View File
@@ -52,6 +52,13 @@ concurrency:
cancel-in-progress: false
env:
# The public registry host, which names the image. Inside the cluster
# GITHUB_SERVER_URL is http://gitea:3000: docker refuses to log in to a
# plain-http registry, and an image named gitea:3000/... is unpullable from
# anywhere that matters. The manifest probe still uses the internal URL —
# same registry, cheaper route. Found by dry-run attempt 4.
REGISTRY_HOST: "git.mial.net"
ZIG_VERSION: "0.16.0"
# Exact patch, not a floating "24" (ruling 12).
NODE_VERSION: "24.19.0"