From bdf46eb91c1948748def909d9dcb4cb6755054d3 Mon Sep 17 00:00:00 2001 From: Hayden Barnes Date: Sun, 31 May 2026 20:34:47 -0400 Subject: [PATCH] ci: make container-image publishing non-blocking The publish-image job builds Windows container images after the binary release. arm64 Windows container images cannot be built on GitHub-hosted windows-11-arm runners (no Docker engine / Windows Containers feature), so that matrix leg always fails and, via matrix fail-fast, was canceling the amd64 image job too. Make image publishing best-effort so it never blocks the win-x64 / win-arm64 binary build and GitHub release: - continue-on-error: true on the publish-image job - fail-fast: false so amd64 completes independently of arm64 The arm64 image leg can light up later once a self-hosted arm64 Windows runner with Docker is available. --- .github/workflows/release.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index cb2a16bcc09..4297cd3599b 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -203,7 +203,14 @@ jobs: publish-image: needs: release + # Container image publishing is best-effort and must never block the binary build/release. + # The win-x64 and win-arm64 runner BINARIES are produced by the build/release jobs above. + # arm64 Windows container images require a self-hosted arm64 Windows host with Docker + # (GitHub-hosted windows-11-arm runners have no Docker installed), so that matrix leg is + # allowed to fail without failing the workflow. + continue-on-error: true strategy: + fail-fast: false matrix: platform: [ windows/amd64, windows/arm64 ] include: