mirror of
https://github.com/headroomlabs-ai/headroom.git
synced 2026-08-27 14:17:10 -04:00
8f6bc5865c
PR #376's per-arch fan-out correctly removed `bake-file-tags` from the docker-build step (tags belong on the multi-arch manifest, not on per-arch images). But that left bake without ANY reference for the push target — no tags AND no explicit `name=` in the output spec. Every release-time docker-build job failed with the misleading message: ERROR: tag is needed when pushing to registry Buildx's actual constraint is "no tags AND no `name=` in the output = no push target." Since push-by-digest discards tags anyway, the fix is to specify `name=<registry>/<image>` directly in the `*.output` spec. Tags are still applied later, only on the multi-arch manifest by `docker-manifest`. Regression test in tests/test_release_workflows.py: `test_docker_per_arch_build_specifies_image_name_in_output` pins the `name=` substring so a future "the labels block already has the registry, surely buildx can figure it out" refactor will fail at PR time rather than 2 minutes into release. |
||
|---|---|---|
| .. | ||
| act | ||
| actions/headroom-e2e-setup | ||
| ISSUE_TEMPLATE | ||
| plugin | ||
| workflows | ||
| dependabot.yml | ||
| FUNDING.yml | ||
| PULL_REQUEST_TEMPLATE.md | ||