mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-17 12:22:34 +03:00
9a3c212b99
The hosted ubuntu-24.04 runner's 7 GB no longer fits the release/v3.8.51 tree — every push to that branch OOMs mid `npm run build` (ResourceExhausted), and the same workflow publishes the release image on the version tag, so a stuck build ships the release without Docker. Route the amd64 build leg to the self-hosted omni-build pool (31 GB) behind the existing USE_VPS_RUNNER repo variable, following the same dynamic-runner expression already used by ci.yml's `build` job and npm-publish.yml's `publish` job (fork-PR guard included verbatim, even though this workflow has no pull_request trigger today). The arm64 leg stays on the hosted ubuntu-24.04-arm runner unchanged and is therefore still at the memory ceiling (tracked separately in #11865).