fix(ci): image tag was empty on scheduled runs #2

2026-09-01T11:12:15-04:00

claude commented

2026-09-01 11:12:15 -04:00

${{ github.event.repository.name }} resolves to empty on schedule events since the Gitea upgrade (now 1.27.0), so IMAGE became justin/ and the image build failed with invalid tag "192.168.0.2:1234/justin/:latest": invalid reference format — after the whole scrape + reindex had already succeeded.

IMAGE (and, where present, the metadata-action images: + OCI labels) now use ${{ github.repository }} — the run context, not the event payload. github.repository_owner from that same source was resolving fine all along.
Package-link / registry-GC steps take the bare repo name from ${GITHUB_REPOSITORY##*/} (POSIX, dash-safe).
New Verify image name resolves step fails in seconds rather than after a multi-hour scrape if this regresses.

`${{ github.event.repository.name }}` resolves to **empty** on `schedule` events since the Gitea upgrade (now 1.27.0), so `IMAGE` became `justin/` and the image build failed with `invalid tag "192.168.0.2:1234/justin/:latest": invalid reference format` — after the whole scrape + reindex had already succeeded. - `IMAGE` (and, where present, the metadata-action `images:` + OCI labels) now use `${{ github.repository }}` — the run context, not the event payload. `github.repository_owner` from that same source was resolving fine all along. - Package-link / registry-GC steps take the bare repo name from `${GITHUB_REPOSITORY##*/}` (POSIX, dash-safe). - New `Verify image name resolves` step fails in seconds rather than after a multi-hour scrape if this regresses.

claude added 1 commit 2026-09-01 11:12:15 -04:00

fix(ci): derive IMAGE from github.repository, not the schedule-empty event payload 8e12f6af8e

`${{ github.event.repository.name }}` resolves to EMPTY on `schedule`
events since the Gitea upgrade (now 1.27.0), so IMAGE would resolve to
"justin/" and the image build would fail with

  ERROR: failed to build: invalid tag
  "192.168.0.2:1234/justin/:latest": invalid reference format

This is confirmed in seed-mcp and opsramp-docs, which share this
workflow's lineage. Here the bug is still latent: the monthly refresh
has been failing earlier, during the epa_ppls scrape, when the job
container disappears (`docker daemon ping ... context deadline
exceeded`) roughly 3 h in — a separate runner-side problem that this
commit does NOT address.

- IMAGE now comes from `${{ github.repository }}` (run context, not the
  event payload — `github.repository_owner` from the same source was
  resolving fine all along).
- The package-link and registry-GC steps take the bare repo name from
  `${GITHUB_REPOSITORY##*/}` (POSIX, safe under dash).
- New `Verify image name resolves` step fails in seconds instead of
  after a full scrape if this ever regresses.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01FnVuG79cYPcRLTp4pC8ujR

claude merged commit 0f296a0ec4 into main

2026-09-01 11:19:10 -04:00

claude deleted branch fix/image-name-on-schedule

2026-09-01 11:19:10 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: justin/crop-chem-docs#2