Both jobs in validate.yml (home-assistant/actions/hassfest@master and hacs/action@main) wrap amd64-only Docker images. On the ARM64 Gitea Actions runner hosting this fork, the images pull successfully but their entrypoints fail with exec format error because no multi-arch image is published.
Guard each job with if: runner.arch != 'ARM64'. GitHub's hosted ubuntu-latest runners are amd64, so the validators still run upstream where they actually matter for HACS distribution. PRs against this Gitea fork will show no CI rather than red CI.
Test plan
After merge, push or open a PR and confirm the run shows both jobs as skipped (gray) rather than failed (red) on Gitea.
If/when the upstream repo (or any amd64 mirror) picks up the change, confirm both jobs still execute normally.
## Summary
Both jobs in `validate.yml` (`home-assistant/actions/hassfest@master` and `hacs/action@main`) wrap amd64-only Docker images. On the ARM64 Gitea Actions runner hosting this fork, the images pull successfully but their entrypoints fail with `exec format error` because no multi-arch image is published.
Guard each job with `if: runner.arch != 'ARM64'`. GitHub's hosted `ubuntu-latest` runners are amd64, so the validators still run upstream where they actually matter for HACS distribution. PRs against this Gitea fork will show no CI rather than red CI.
## Test plan
- [ ] After merge, push or open a PR and confirm the run shows both jobs as skipped (gray) rather than failed (red) on Gitea.
- [ ] If/when the upstream repo (or any amd64 mirror) picks up the change, confirm both jobs still execute normally.
The hassfest and HACS validator actions both depend on amd64-only
Docker images (ghcr.io/home-assistant/hassfest, hacs/action). On
ARM64 runners — like the Gitea Actions instance hosting this fork —
those images pull but fail with "exec format error" because no
multi-arch image is published.
Validation still runs on GitHub's amd64 ubuntu-latest runners, where
it actually matters for HACS distribution.
The runner.arch context isn't populated for job-level if conditions
on Gitea Actions, so the previous guard didn't skip on ARM64 Gitea
runners. Switch to checking github.server_url, which is reliably
'https://github.com' on GitHub-hosted runs and the Gitea host
everywhere else.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Both jobs in
validate.yml(home-assistant/actions/hassfest@masterandhacs/action@main) wrap amd64-only Docker images. On the ARM64 Gitea Actions runner hosting this fork, the images pull successfully but their entrypoints fail withexec format errorbecause no multi-arch image is published.Guard each job with
if: runner.arch != 'ARM64'. GitHub's hostedubuntu-latestrunners are amd64, so the validators still run upstream where they actually matter for HACS distribution. PRs against this Gitea fork will show no CI rather than red CI.Test plan