💡 ARM64 Runner Migration for Fleet-Wide CI Cost Reduction

[github-actions[bot]]

Summary

GitHub shipped ARM64 hosted runners for private repos (January 2026) with up to 39% pricing cuts on runner minutes. This org's CI is overwhelmingly bash/jq/Python shell orchestration with zero x86 binary dependencies. Migrating applicable workflows to ARM64 runners (ubuntu-24.04-arm) would deliver immediate CI cost savings with minimal risk, as a phased rollout starting with the least-critical scheduled workflows.

Market Signal

GitHub announced ARM64 standard runners for private repos on Jan 29, 2026, with up to 39% rate cuts effective Jan 1, 2026. Ubuntu 26.04 just went GA for Actions (Sep 17, 2026). The broader industry trend toward ARM (AWS Graviton, Apple Silicon, Azure Cobalt) means tooling compatibility is converging rapidly. GPU larger runners on ARM remain available on Team/Enterprise Cloud plans.

User Signal

• The org runs 10+ scheduled bash-only workflows daily (fleet monitor, health checks, auto-rebase health, premature-closure audit, docs-health-check, validate-workflow-schedules, token report, skill-eval report, reviewer report).
• Token cost reports (token-report.yml) show LLM spend dominates, but runner-minute costs for the non-LLM pure-bash/jq workflows are independent infrastructure spend that can be optimized.
• Cost awareness is growing: Action Budget slices (Action budget, slice 1 of 3: emit structured per-run timing (elapsed vs budget) for every dev-lead run #1658, Action budget, slice 2 of 3: report the elapsed-vs-budget distribution and alert on genuine near-misses #1659, Action budget, slice 3b: resume from a checkpoint on re-dispatch (or say why not) #1706) and the Sonnet 5 price tracking show active attention to cost optimization.

Technical Opportunity

All scripts in scripts/ use #!/usr/bin/env bash with standard POSIX tools (jq, curl, gh, python3). None depend on x86 binaries. A phased migration:

1. Pilot: Run one scheduled bash-only workflow on ARM64 (e.g., premature-closure-audit.yml)
2. Measure: Compare timing + cost against x86 baseline
3. Widen: Migrate all bash/jq-only workflows
4. Evaluate: Assess LLM-invoking workflows pending claude-code-action ARM64 support

Assessment

Dimension	Score	Rationale
Feasibility	high	Zero code changes for bash-only workflows; runs-on: swap only
Impact	high	Up to 39% runner cost savings across 10+ daily scheduled workflows
Urgency	med	Cost savings compound daily; no blocking dependency for first wave

Adversarial Review

Strongest objection: The claude-code-action (Anthropic's official Action) may not support ARM64. If the Action's container image is x86-only, the LLM-invoking workflows (dev-lead, pr-review — the majority of compute spend) can't migrate.

Rebuttal: The phased approach explicitly separates bash-only workflows (fleet monitor, health checks, auto-rebase health, premature-closure audit — all pure gh/jq/curl with no LLM) from LLM-invoking workflows. The first wave is risk-free: no binary dependencies, no Actions that aren't built-in shell tools. Even if only bash-only workflows migrate, the savings are meaningful for an org running 10+ scheduled workflows daily. The second wave tracks claude-code-action ARM64 support as a gating dependency.

Suggested Next Step

Audit the 10+ scheduled bash-only workflows for ARM64 compatibility (check each Action's supported architectures). Pilot one workflow (e.g., premature-closure-audit.yml) on ubuntu-24.04-arm for one week. Measure runner-minute cost delta. If positive, open a fleet-migration tracking issue.