From 9206c480b2894a5d948919948ac3f240ac8119ea Mon Sep 17 00:00:00 2001 From: Huarch Date: Fri, 24 Apr 2026 15:54:03 +0800 Subject: [PATCH] ci: lowercase image repository Normalize github.repository to lowercase before composing Docker image tags so Gitea registry references stay valid on the runner. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .gitea/workflows/package.yml | 1 + memery.md | 2 ++ 2 files changed, 3 insertions(+) diff --git a/.gitea/workflows/package.yml b/.gitea/workflows/package.yml index b44671b..790f6ec 100644 --- a/.gitea/workflows/package.yml +++ b/.gitea/workflows/package.yml @@ -59,6 +59,7 @@ jobs: REGISTRY_HOST="${REGISTRY_HOST#https://}" REGISTRY_HOST="${REGISTRY_HOST%/}" REPOSITORY_PATH="${RAW_REPOSITORY#/}" + REPOSITORY_PATH="$(printf '%s' "$REPOSITORY_PATH" | tr '[:upper:]' '[:lower:]')" IMAGE_NAME="${REGISTRY_HOST}/${REPOSITORY_PATH}" case "$IMAGE_TAG" in *-test) IS_TEST_TAG=true ;; diff --git a/memery.md b/memery.md index fb9ecac..edf3e3c 100644 --- a/memery.md +++ b/memery.md @@ -9,5 +9,7 @@ - **Root cause found on the real act_runner:** although the runner was registered with `ubuntu:docker://gitea/runner-images:ubuntu-22.04`, the workflow used `runs-on: ubuntu`, and the job log showed `Start image=ubuntu:latest`. That default image does not include the expected toolset, which explains the remote `git: not found` failure. - **Applied fix for label selection:** changed both jobs to `runs-on: "ubuntu:docker://gitea/runner-images:ubuntu-22.04"` so Gitea resolves the exact runner image instead of falling back to `ubuntu:latest`. - **Follow-up from server validation:** Gitea then reported `No matching online runner with label: ubuntu:docker://gitea/runner-images:ubuntu-22.04`. The runner advertises the short label `ubuntu-22.04`, so the workflow was updated again to use `runs-on: ubuntu-22.04`, which should map to `docker://gitea/runner-images:ubuntu-22.04` on the runner side. +- **Next remote failure on act_runner:** Docker rejected the tag `gitea.waternetwork.cn/OrgTJWater/TJWaterFrontend_Refine:v2026.04.24-test3` with `repository name must be lowercase`. The workflow had normalized the registry host but not the repository path from `github.repository`. +- **Applied fix for image naming:** lowercased `REPOSITORY_PATH` during image metadata normalization so image tags remain valid even when the Gitea owner or repository name contains uppercase letters. - **Current local result:** `npm run lint`, `npm run test -- --runInBand`, `npm run build`, `docker build ...`, and `npm run build` inside `gitea/runner-images:ubuntu-22.04` all completed successfully after the workflow adjustment. - **Non-blocking note:** local Jest run reported a haste-map naming collision between `package.json` and `.next/standalone/package.json`; tests still passed, and this does not affect the current image-build workflow.