forust ac0f845da6 fix(deploy): stop the panel from pointing at a tag the build dropped ...

USERBOT_IMAGE named userbot:latest, but the build stopped pushing latest when
images became :prod. render_pinned resolves every gcr.forust.xyz reference it
finds in a manifest, not just the ones it rewrites, so that env var made the
whole apply abort with "cannot resolve userbot:latest; applying nothing".

Naming it :prod also makes the build job rebuild userbot, which is what
restores forust/userbot:prod - the tag is listed in the registry but its
manifest 404s, so the image: field in userbots.yaml had nothing to resolve
either.

Found by resolving every digest apply-k8s will need before spending a run on
it: 6 of 8 resolved, and both failures were userbot.

2026-09-27 16:14:43 +02:00

..

common-config.yaml

Merge commit '3eaef5dc90b716cc0fa391cbe2394be56d5f6041' as 'userbot'

2026-06-19 23:20:23 +02:00

internal-certificate.yaml

feat(tls): internal CA wildcard for *.internal routes

2026-09-23 14:45:05 +02:00

kustomization.yaml

fix(userbot): include internal-certificate in kustomize base

2026-09-23 15:52:32 +02:00

panel.yaml

fix(deploy): stop the panel from pointing at a tag the build dropped

2026-09-27 16:14:43 +02:00

userbots.yaml

fix(deploy): roll out our images by digest instead of a moving tag

2026-09-27 10:09:06 +02:00