Bug: linux/arm64 image is never built #5429

🐛 Bug: linux/arm64 image is never built

Description

The matrix exclude condition in .github/workflows/docker-build.yml contains a logic error that causes linux/arm64 to be excluded on every trigger — tag pushes and branch pushes alike. As a result, no ARM image has ever been built or pushed.

Root Cause

exclude:
  - platform: ${{ github.ref != 'tag' && 'linux/arm64' }}

github.ref holds the full Git ref path (e.g. refs/heads/main, refs/tags/v1.0.0). It will never equal the bare string 'tag', so the expression is always true and linux/arm64 is permanently excluded from the matrix.

Impact

• Every published multi-arch manifest actually contains only linux/amd64
• ARM devices (Raspberry Pi, Apple Silicon hosts, AWS Graviton, etc.) silently fall back to the amd64 layer, causing degraded performance or outright failure
• All historical releases are affected

Steps to Reproduce

1. Push any v* tag
2. Check the Actions run — the linux/arm64 matrix entry is absent from make-upload-docker
3. Run docker buildx imagetools inspect ghcr.io/hiddify/hiddify-manager:<tag> and confirm only amd64 appears in the manifest

Proposed Fix

Remove the broken exclude block and raise timeout-minutes from 10 to 60 (ARM cross-compilation via QEMU typically takes 5–10× longer than amd64):

strategy:
  fail-fast: true
  matrix:
    platform:
      - linux/amd64
      - linux/arm64
      # exclude block removed

Optional: If you want to build arm64 only on tag pushes to save CI minutes, the reliable approach is a step-level condition rather than a matrix exclude expression (matrix excludes have incomplete support for context variables in GitHub Actions):

- name: Build and push by digest
  if: matrix.platform != 'linux/arm64' || github.ref_type == 'tag'

Expected Behavior

After pushing a v* tag, the manifest for ghcr.io/hiddify/hiddify-manager should list both linux/amd64 and linux/arm64 platforms.