Fix Docker Hub image publishing workflow#640
Merged
brunobuddy merged 1 commit intomainfrom Jan 22, 2026
Merged
Conversation
The Docker publish workflow wasn't triggering because GITHUB_TOKEN pushes don't create new workflow runs (GitHub security measure). Changes: - Add workflow_call trigger to manifest-publish.yml with version input - Update release.yml to call docker-publish directly after tagging - Replace docker/metadata-action with custom tag generation script - Add explicit OCI labels to the Docker build step The release workflow now explicitly calls the Docker publish workflow after creating the version tag, ensuring Docker images are published.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
|
🚅 Deployed to the manifest-pr-640 environment in Manifest
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Docker publish workflow wasn't triggering because GITHUB_TOKEN pushes don't create new workflow runs (GitHub security measure).
Changes:
The release workflow now explicitly calls the Docker publish workflow after creating the version tag, ensuring Docker images are published.