ci: add github action to publish a docker image for each new release#65
Open
Maistho wants to merge 1 commit intomelodee-project:mainfrom
Open
ci: add github action to publish a docker image for each new release#65Maistho wants to merge 1 commit intomelodee-project:mainfrom
Maistho wants to merge 1 commit intomelodee-project:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds an automated GitHub Actions workflow to build and publish multi-architecture Docker images to GitHub Container Registry (GHCR) whenever a GitHub Release is published, addressing the request for prebuilt images (Fixes #64).
Changes:
- Added a new
docker-publish.ymlworkflow that buildslinux/amd64andlinux/arm64images and publishes a multi-platform manifest to GHCR on release publish. - Documented the new workflow in
AGENTS.mdalongside existing CI/CD workflows.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| AGENTS.md | Adds the new Docker publish workflow to the repo’s documented workflow list. |
| .github/workflows/docker-publish.yml | Implements release-triggered multi-arch Docker build + push to GHCR with manifest creation. |
sphildreth
approved these changes
Mar 30, 2026
Collaborator
sphildreth
left a comment
sphildreth
left a comment
There was a problem hiding this comment.
We probably should add something to the root README about having pre-built containers now. Thanks again!
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
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.
Fixes #64
Tested by running the action on my fork and then installing image in my k8s cluster, you should be able to see the build logs etc here: https://github.com/Maistho/melodee/actions/runs/23720015365
The built package here: https://github.com/Maistho/melodee/pkgs/container/melodee
Just built some bogus releases (1.2.3, then 1.2.4 and 1.2.5 to test)
I'm not sure how you would want to update the documentation, I guess in the future it would make sense to update the compose file that people are recommended to just link against that image instead of having to build the image themselves.