Skip to content

ci(release): build each container architecture on its native runner - #60

Merged
CN059 merged 1 commit into
mainfrom
dev
Nov 21, 2026
Merged

CN059 merged 1 commit into
mainfrom
dev

Conversation

@CN059

@CN059 CN059 commented Nov 21, 2026

Copy link
Copy Markdown
Member

Summary

v0.6.0 published every installer and archive, but no container image.

The multi-arch push built arm64 under QEMU on an amd64 runner. Compiling the
whole workspace at QEMU speed consumed the entire 60-minute timeout-minutes
bound; the job was cancelled at 08:28:28Z. v0.5.4 finished the same step in 53
minutes, so the bound was already the binding constraint rather than a safety
net.

Change

Split by architecture instead of raising the timeout:

  • container is now a matrix: amd64 on ubuntu-latest, arm64 on
    ubuntu-24.04-arm (the runner build already uses). Each pushes an
    arch-suffixed tag with its own GHA cache scope.
  • container-manifest combines them into X.Y.Z, X.Y, and latest with
    buildx imagetools create — manifests by digest, no layers re-uploaded.
  • The offline startup check moved to its own container-smoke job. It still
    gates the image jobs, but no longer shares their timeout.

release still does not depend on the container jobs: a broken image must not
withhold installers, it only fails the run.

Verification

  • YAML parses; job graph is verify-tag → {container-smoke → container → container-manifest} and {build, desktop} → release.
  • actionlint reports no new findings; only the two pre-existing
    windows-11-vs2026-arm label notes (that job succeeded in this release).
  • The workflow only runs on a tag, so the real proof is the next release tag.

Note

The v0.6.0 tag still has no image. After this merges, ghcr.io/tatencn/rustfrp:0.6.0
needs one of: a re-run of the release workflow on that tag (which would also
rebuild the installers), or a manual docker buildx push from a checkout of the
tag.

The v0.6.0 release published every installer and archive but no container
image: the multi-arch push runs arm64 under QEMU on an amd64 runner, and
compiling the whole workspace at QEMU speed took the entire 60-minute
bound. v0.5.4 finished the same step in 53 minutes, so the margin was
already gone; this release was cancelled at the bound.

Split it by architecture instead of raising the timeout:

- `container` becomes a matrix over amd64 (`ubuntu-latest`) and arm64
  (`ubuntu-24.04-arm`, already used by `build`), each pushing an
  arch-suffixed tag with its own cache scope.
- `container-manifest` combines the two into the unsuffixed version,
  major.minor, and `latest` tags via `imagetools create`, which copies
  manifests by digest and moves no layers.
- The offline startup check moves to its own `container-smoke` job, still
  gating the image jobs but no longer sharing their timeout.

`release` still does not depend on the container jobs: a broken image must
not withhold installers, it only fails the run.
@CN059
CN059 merged commit 44526bd into main Nov 21, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant