GitHub-hosted larger runners pick up RHEL 9 and RHEL 10 in public preview

GitHub's hosted larger runners now boot Red Hat Enterprise Linux 9 and RHEL 10 images in public preview, and for any shop that has stood up its own runner pool just to keep production-like CI on Red Hat, the operational read is straightforward: a real chunk of that pool can go back to being someone else's pager. GitHub announced the change on its changelog on June 25, 2026, and credits the work as a partnership with Red Hat.

What the changelog actually says

Two image families, RHEL 9 and RHEL 10, on the larger-runner tier. Status is public preview, which is its own asterisk. There is no SLA pinned to a preview image, the surface will move while the team irons it out, and the changelog frames the source as Red Hat itself, with no mention of a community rebuild.

Where this lands on the on-call shift

The pitch is easy to read. Regulated and enterprise shops that standardised on Red Hat have been running self-hosted Actions for exactly one reason: matching their production base image. That work is real on-call cost. Pool sizing, CVE backports, kernel rolls, agent upgrades, and a steady drip of "why did our runner go offline at 02:14 again" tickets. A hosted RHEL image swaps that for someone else's pager and a per-minute line item.

The catch is upstream of the price sheet. This is the larger-runner tier, which is paid, so the cost story does not look like the free Ubuntu runners most public-repo workflows lean on. And public preview means the failure mode you do not want to discover during an audit window is exactly the one you will find first. Three questions the changelog does not answer: which minor channel the hosted image tracks, how often it rolls, and what the deprecation window looks like when RHEL 9 eventually ages out. Until those land, the safe move is to migrate workloads where a slipped image is annoying but recoverable, and to leave FIPS-bound or compliance-locked builds where they already run.