The Sengi label in runs-on can come from an expression
What changed?
The guide and docs now say the Sengi label in runs-on can come from a GitHub Actions expression or variable, so one variable can choose the runner for many workflows. The service terms say the same.
Details
The guide, the runner sizes page and the troubleshooting page used to tell you to write the label out literally. They now describe using an expression or variable that resolves to one Sengi label; the troubleshooting page explains how to read the resolved value in the job log. Section 3.4 of the terms was updated to match.
Each job still takes exactly one Sengi label. Automated setup still rewrites only labels that are written out, so a label from an expression needs to be set by hand.
Related pages
More changes
- Next: New pages comparing hosted runner services (Nov 16, 2026)
- Previous: Terms list the Basic and Premium runner labels (Nov 13, 2026)
- All changes in the Sengi changelog
Keep your workflow. Cut your runner rate.
Sengi Basic starts at $0.001 a minute for 2 vCPU. Choose 4 or 8 vCPU for $0.002 or $0.004 a minute. Premium stays optional at $0.003, $0.006 and $0.012.
Start without a card ↗︎