feat(docker): Add GHCR workflow for backend and frontend package releases#994
Open
kapdon wants to merge 1 commit intomultica-ai:mainfrom
Open
feat(docker): Add GHCR workflow for backend and frontend package releases#994kapdon wants to merge 1 commit intomultica-ai:mainfrom
kapdon wants to merge 1 commit intomultica-ai:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
kapdon
changed the title
kapdon
changed the title
Self-hosted deployments already build backend and frontend images from the repository's Dockerfiles, but release automation only published CLI artifacts. This adds a dedicated GitHub Actions workflow that publishes GHCR images for both build targets on the existing v* release cadence with version and latest tags. Constraint: Keep docker-compose and self-hosting docs unchanged in this PR Constraint: Use GitHub Container Registry and the existing v* tag release flow Rejected: Fold container publishing into the GoReleaser workflow | keeps container concerns separate and reviewable Rejected: Add SHA image tags | user requested only version aliases and latest Confidence: high Scope-risk: narrow Reversibility: clean Directive: If release tagging changes later, update both CLI and Docker release workflows together Tested: yaml.safe_load on .github/workflows/docker-release.yml Tested: actionlint via rhysd/actionlint Docker image Tested: docker build -f Dockerfile -t multica-backend:test . Tested: docker build -f Dockerfile.web -t multica-frontend:test . Not-tested: Actual GHCR publish from GitHub Actions on a real v* tag Not-tested: Multi-arch push execution on GitHub-hosted runners
kapdon
force-pushed
the
codex/docker-ghcr-release-workflow
branch
from
d7cfadf to
5ef84c2
Compare
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.
What does this PR do?
Adds a dedicated GitHub Actions workflow that publishes the backend and frontend Docker images to GitHub Container Registry on the existing
v*tag release flow.Related Issue
Closes #
Type of Change
Changes Made
.github/workflows/docker-release.ymlmultica-backendfromDockerfilemultica-frontendfromDockerfile.webv*tag pusheslatestHow to Test
docker run --rm -v "$PWD":/repo -w /repo rhysd/actionlint:latestdocker build -f Dockerfile -t multica-backend:test .docker build -f Dockerfile.web -t multica-frontend:test .v*tag in a repo with GHCR package publish permissions and confirm both images are publishedChecklist
AI Disclosure
AI tool used: OpenAI Codex CLI
Prompt / approach:
Used a deep-interview clarification pass to lock the registry, trigger, package names, and tag policy, then implemented the smallest additive GHCR release workflow and validated it with actionlint plus local Docker builds for both images.
Screenshots (optional)
N/A