joakimp 034830710c workflow: use github.ref_type directly in promote/update-description if-conditions ...

Gitea Actions evaluates 'env.PROMOTE_LATEST' as empty in YAML 'if:'
contexts even though the same env var substitutes correctly in
shell run: blocks. Result: on v1.15.0/v1.15.0b tag pushes, the
build-variant-* jobs correctly pushed latest-* aliases (shell context),
but promote-base-latest and update-description got skipped (YAML
context), so the Hub README description wasn't refreshed.

Switch to evaluating github.ref_type directly in the if-conditions —
matches the production-trigger semantics and avoids the env-var
indirection that gitea evaluates inconsistently.

2026-05-15 13:50:46 +02:00

..

docker-publish-split.yml

workflow: use github.ref_type directly in promote/update-description if-conditions

2026-05-15 13:50:46 +02:00

validate.yml

validate.yml: use Hub base-latest as variant parent + warn on base-input changes

2026-05-14 20:53:19 +02:00