Skip to content

docker: drop push-tag trigger; workflow_run is the only canonical path#11

Merged
valani9 merged 1 commit into
mainfrom
docker-drop-push-tag-trigger
May 25, 2026
Merged

docker: drop push-tag trigger; workflow_run is the only canonical path#11
valani9 merged 1 commit into
mainfrom
docker-drop-push-tag-trigger

Conversation

@valani9
Copy link
Copy Markdown
Owner

@valani9 valani9 commented May 25, 2026

Summary

v0.5.0 docker.yml shipped GHCR image successfully via the workflow_run path. But the parallel push-tag-triggered run failed at 28s because dist/ + PyPI were both still empty when it started.

Fix: remove the push-tag trigger entirely. workflow_run already covers the release case (and is the only path with the wheel artifact actually available); workflow_dispatch covers manual retries.

Test plan

  • workflow_run path verified successful for v0.5.0 (run 26402061869, ghcr.io/valani9/vstack:0.5.0 + :0.5 + :0 + :latest published)
  • Next release will only trigger one docker run via workflow_run
  • manual workflow_dispatch retries still work

The v0.5.0 release surfaced one more failure mode in docker.yml.
When a v*.*.* tag is pushed, GitHub fires release.yml AND docker.yml
in parallel. The push-tag-triggered docker run starts immediately:
  - dist/ doesn't yet contain the wheel (release.yml is still
    building it)
  - PyPI doesn't yet have the new version (release.yml hasn't
    published yet)

Both paths in the Dockerfile fail and the build dies at ~28s.

The workflow_run-triggered run starts AFTER release.yml completes
successfully, downloads the release-dist artifact (now exists),
and installs from the local wheel. That path just shipped
ghcr.io/valani9/vstack:0.5.0 cleanly.

Fix: drop the push-tag trigger entirely. workflow_run is the only
release trigger; workflow_dispatch stays for manual retries.
Eliminates the always-failing parallel run on every release.
@valani9 valani9 merged commit 8ce98e7 into main May 25, 2026
10 checks passed
@valani9 valani9 deleted the docker-drop-push-tag-trigger branch May 25, 2026 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant