CI: add release multi-arch workflow for git-bridge image#34
Merged
Musicminion merged 1 commit intoserver-profrom Mar 13, 2026
Merged
Conversation
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.
Motivation
git-bridgeservice so release pipelines produce bothlinux/amd64andlinux/arm64artifacts.Description
.github/workflows/build_release_image.yml:build_git_bridgeto build and upload per-architecture images fromservices/git-bridge/Dockerfileandmerge_git_bridgeto create and push a multi-arch manifest forghcr.io/.../git-bridgewithlatestand release-version tags.build_git_bridgeruns forlinux/amd64andlinux/arm64, extracts the latestrelease-v*ref, setsversion, runsdocker/build-push-action@v6withcontext: ./services/git-bridge, and uploads digest artifacts per-arch.merge_git_bridgedownloads the per-arch digest artifacts and usesdocker buildx imagetools createto assemble and push the manifest, then runs animagetools inspectand retention cleanup foroverleaf-pro/git-bridge.services/git-bridge/Dockerfilewas inspected and left unchanged, and the workflow reuses metadata labels and registry login consistent with the existing release jobs.Testing
ruby -e "require 'yaml'; YAML.load_file('.github/workflows/build_release_image.yml'); puts 'ok'", which returnedokindicating valid YAML.PyYAMLcausing theModuleNotFoundError, which is an environment issue and not a workflow error.ci: add multi-arch release workflow for git-bridge image).Codex Task