0xWheatyz 04597a9ed6 ci(docker): publish sortable <timestamp>-<sha> tag for Flux image automation ...

Both image workflows now emit a <timestamp>-<sha> tag on main pushes
alongside the existing sha-<short>/latest tags. Flux's ImagePolicy needs a
sortable tag to pick the newest build; latest is mutable and sha-<short>
has no ordering, so neither could drive auto-deploy. Same scheme as the
Talos devbox image.

Tag is stamped at build time (UTC); re-running a stale build would sort
newest, so prefer reverting over re-running. api and control build via
separate workflows/policies and can skew if one fails.

2026-07-18 15:24:28 -04:00

..

docker-control.yml

ci(docker): publish sortable <timestamp>-<sha> tag for Flux image automation

2026-07-18 15:24:28 -04:00

docker.yml

ci(docker): publish sortable <timestamp>-<sha> tag for Flux image automation

2026-07-18 15:24:28 -04:00