forust 6a9a460769 fix(deploy): let a pinning failure explain itself ...

registry_digest was written to return an empty string for a ref the registry
does not have, so render_pinned could print "cannot resolve <ref>" and stop.
It could not do that. Every caller runs under set -euo pipefail, pipefail
reports the rightmost non-zero stage, and the failed docker manifest inspect
made the assignment itself fail, which set -e turns into an immediate exit.

render_pinned therefore died silently on the first unresolvable ref: nothing on
stderr, nothing on stdout, exit 1. The apply loop piped that empty stream into
kubectl, so the whole deploy stopped with "error: no objects passed to apply" -
kubectl guessing at a cause, with the actual reason nowhere in the log. The
missing message is the reason the f54589a run looked like a network death.

Reproduced against the old file with a docker stub that always fails: identical
to the ac0f845 log. The || true makes the empty string reachable, and the apply
loop now names the file that failed instead of letting kubectl speak.

2026-09-27 16:33:37 +02:00

..

workflows

fix(deploy): let a pinning failure explain itself

2026-09-27 16:33:37 +02:00

actionlint.yaml

ci: lint workflows and shell scripts, validate k8s against the API server

2026-09-26 20:09:09 +02:00