kevinveenbirkenbachandClaude Opus 5 329f43097c fix(ci): make the image job prove the images exist before it reports success ...

For a fork PR the build step is skipped -- the images come from the
privileged run -- so the job went green in 29 seconds while that run was
still pushing. Everything gated on it inherited the lie: the DNS test
pulled arch 3m30s too early on one run and 53s too early on the next,
both times 'manifest unknown', and the four deploy chunks were spared
only by starting later.

The job now polls until every distro image for its tag is in the
registry. It runs unconditionally: where the job built the images itself
the first poll passes, and a push that silently failed is caught too.

The poll drives scripts/meta/resolve/missing/ci_images.sh, which already
owned that check for the release workflow, so the ref shape is not
written a fourth time. A resolver that cannot run aborts with 2 rather
than reading as 'not yet pushed' and hiding behind the full budget.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-17 00:31:33 +02:00

..

env

fix(env): point python at the OS trust store

2026-08-22 18:55:58 +02:00

mirror/sync

refactor(structure): nest prefix-grouped sibling files into subfolders

2026-07-14 20:00:03 +02:00

resolve

feat(ci): spread distro and filesystem per row

2026-08-20 14:23:29 +02:00

wait

fix(ci): make the image job prove the images exist before it reports success

2026-09-17 00:31:33 +02:00