ci(docker): publish multi-architecture images - #432
Open
neobuilds wants to merge 1 commit into
Open
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.
Summary
latesttagsimagejob output consumed by the release-bundle job0.0.17changelogWhy
Instatic originally configured QEMU-based AMD64 + ARM64 publishing, then intentionally limited releases to AMD64 in
b8dda9acbecause emulated ARM64 publishing made the tagged workflow too slow.This follows the repository's documented intended fix: each architecture builds on a separate native GitHub-hosted runner (
ubuntu-latestandubuntu-24.04-arm). The final job merges the platform digests into one OCI image index, so the release gate does not run the application build under QEMU.Verification
actionlint .github/workflows/release.yml— passedbun run lint— passedbun run build— passed/healthpassed/healthpassedlinux/amd64andlinux/arm64docker buildx build --check --platform linux/amd64,linux/arm64 .— passed with no warningsgit diff --check— passedThe tag-triggered GHCR publication cannot be exercised end to end from the fork because the workflow intentionally publishes to the upstream
corebunchpackage namespace. The platform images, native runtime dependencies, and manifest-merge operation were verified separately as listed above.