From 4e061ef53d7b66723217e36d9956be98c70e96ad Mon Sep 17 00:00:00 2001 From: Aaron Sachs <898627+asachs01@users.noreply.github.com> Date: Tue, 8 Sep 2026 04:34:02 +0000 Subject: [PATCH] fix(ci): retarget release GHCR image to our own org namespace release.yml's docker/metadata-action was still hardcoded to ghcr.io/corebunch/instatic (upstream's own package), unmodified since this repo was forked. A real tag-triggered release would have tried to publish into a namespace we don't own instead of landing anywhere we control. Computed the image path from github.repository, lowercased, using the same fix already shipped in WYRE-AI/conduit's deploy.yml after that repo's own org move broke an equivalent hardcoded/case-sensitive ref. --- .github/workflows/release.yml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 352baf304..2ef72757f 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -63,11 +63,24 @@ jobs: username: ${{ github.actor }} password: ${{ github.token }} + # `github.repository` is not guaranteed lowercase (this fork lives under + # WYRE-AI), and GHCR image refs must be — same fix already applied in + # WYRE-AI/conduit's deploy.yml after that repo's own org move produced + # an invalid `ghcr.io/WYRE-AI/conduit` ref. Computed once here so the + # image tag can't silently point at upstream's own corebunch/instatic + # package again. + - name: Resolve GHCR image repo + id: repo + env: + REPO: ${{ github.repository }} + run: | + echo "image=$(printf '%s' "$REPO" | tr '[:upper:]' '[:lower:]')" >> "$GITHUB_OUTPUT" + - name: Extract Docker metadata id: meta uses: docker/metadata-action@v5 with: - images: ghcr.io/corebunch/instatic + images: ghcr.io/${{ steps.repo.outputs.image }} tags: | type=semver,pattern={{version}} type=semver,pattern={{major}}.{{minor}}