Repository navigation
Conversation
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.
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
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-minutesbound; 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:
containeris now a matrix: amd64 onubuntu-latest, arm64 onubuntu-24.04-arm(the runnerbuildalready uses). Each pushes anarch-suffixed tag with its own GHA cache scope.
container-manifestcombines them intoX.Y.Z,X.Y, andlatestwithbuildx imagetools create— manifests by digest, no layers re-uploaded.container-smokejob. It stillgates the image jobs, but no longer shares their timeout.
releasestill does not depend on the container jobs: a broken image must notwithhold installers, it only fails the run.
Verification
verify-tag → {container-smoke → container → container-manifest}and{build, desktop} → release.actionlintreports no new findings; only the two pre-existingwindows-11-vs2026-armlabel notes (that job succeeded in this release).Note
The
v0.6.0tag still has no image. After this merges,ghcr.io/tatencn/rustfrp:0.6.0needs one of: a re-run of the release workflow on that tag (which would also
rebuild the installers), or a manual
docker buildxpush from a checkout of thetag.