Summary
Versioned Docker image tags (e.g., 1.5.3, v1.5.3) are not being published to GHCR, even though releases are created via semantic-release.
Current Behavior
- On merge to
main:
build-docker.yml publishes main and latest images
release.yml creates a Git tag (e.g., v1.5.3)
- Docker images for the release tag are not published
Root Cause
- Release tags are created using
GITHUB_TOKEN
- GitHub does not trigger workflows from events caused by
GITHUB_TOKEN
- As a result, the build workflow does not run for the new tag
Proposed Solution
- Move Docker image publishing into
release.yml after semantic-release
- Keep
build-docker.yml for main and latest images
- Tag release images with:
Source from GitHub: When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN, with the exception of workflow_dispatch [manually triggered] and repository_dispatch [triggered via API], will not create a new workflow run. (ours is push event)
In the short term, can you please trigger build-docker.yml manually so we have the tag available in GHCR. Thanks!

Summary
Versioned Docker image tags (e.g.,
1.5.3,v1.5.3) are not being published to GHCR, even though releases are created viasemantic-release.Current Behavior
main:build-docker.ymlpublishesmainandlatestimagesrelease.ymlcreates a Git tag (e.g.,v1.5.3)Root Cause
GITHUB_TOKENGITHUB_TOKENProposed Solution
release.ymlaftersemantic-releasebuild-docker.ymlformainandlatestimages1.5.3v1.5.3Source from GitHub: When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN, with the exception of workflow_dispatch [manually triggered] and repository_dispatch [triggered via API], will not create a new workflow run. (ours is
pushevent)In the short term, can you please trigger
build-docker.ymlmanually so we have the tag available in GHCR. Thanks!