Commit Graph

3 Commits

Author SHA1 Message Date
npub1mn7jgtj4w2pd0g0zeuhxsa6jy6p0rewxz4kujt98my82ahfmp72sxjexk7
c045e9b74f fix(ci): publish versioned Docker tags via auto-tag dispatch
Auto-tagged releases never published versioned container images. The
release tag is pushed with the default GITHUB_TOKEN, and GitHub's
recursion guard suppresses all on:push triggers for GITHUB_TOKEN-pushed
refs, so docker.yml's on:push:tags trigger never fired. Only :main and
:latest existed; every ghcr.io/block/buzz:vX.Y.Z returned 404.

Mirror the rescue release.yml already uses: auto-tag now dispatches
docker.yml with version+ref. On dispatch github.ref is main, so the tag
ref is plumbed through explicitly — checkout pins to inputs.ref and the
type=semver tags take inputs.version via metadata-action value=. An
empty value= is a no-op on the native push-tag path (procSemver falls
back to the git ref), so human-pushed tags and inputless canary
dispatches are unchanged.

Co-authored-by: Will Pfleger <pfleger.will@gmail.com>
Signed-off-by: Will Pfleger <pfleger.will@gmail.com>
2026-06-20 15:35:27 -04:00
Will Pfleger
39d9aa8260 ci: add fork guards to docker, release, and auto-tag workflows (#1007) 2026-06-12 13:53:43 -04:00
tlongwell-block
1fa63badad ci(docker): publish public ghcr.io/block/buzz image (native multi-arch) (#986)
Signed-off-by: Tyler Longwell <tlongwell@squareup.com>
Co-authored-by: npub17jjz49l9jjmhhk7cac63j8yt9z555n9cw8vk7v5jz4vzw4ppld5qgj57cc <f4a42a97e594b77bdbd8ee35191c8b28a94a4cb871d96f32921558275421fb68@sprout-oss.stage.blox.sqprod.co>
2026-06-12 11:20:44 -04:00