GitHub Actions: Self-hosted runner minimum version enforcement extended
Editor’s note (February 20, 2026): We updated this post to clarify that the v2.329.0 minimum version requirement applies at configuration/registration time (before running ./config.sh), not as the minimum version required for runners to execute workflows. We also extended the configuration-time enforcement deadline by one week to March 16, 2026, adjusted the brownout schedule times accordingly, and clarified that GitHub Enterprise Server (GHES) customers are not impacted by this change.
We’ve extended the timeline for configuration-time (registration-time) version enforcement of the minimum self-hosted runner requirement by one week. You now have until March 16, 2026 to ensure your runners are on v2.329.0 or later before running ./config.sh (configuring/registering the runner).
This extends the timeline we shared in our December 2025 announcement. This change applies to the minimum runner version required to configure/register a self-hosted runner. Separately, runners must also be kept up to date according to the self-hosted runner update policy in our documentation (for example, workflows may stop being queued to runners that are too far out of date). This change applies to GitHub.com only. GitHub Enterprise Server (GHES) customers are not impacted at this time.
What’s changing
Starting March 16, 2026, GitHub Actions will block runner configuration/registration from self-hosted runners older than v2.329.0 (released October 15, 2025). Between February 23 and March 16, we’ll run a brownout period with scheduled configuration blocks to help you identify runners that need updates.
After March 16, runners must meet the minimum version requirement to register. Older runners won’t be able to connect or self-upgrade after running the configuration script.
Brownout schedule
During the brownout period, we’ll temporarily block runner configuration/registration from runners below v2.329.0. This table shows when blocks will occur in major timezones:
| Week | Date and Time (UTC) |
|---|---|
| 1 | February 23 (Mon), 15:00-17:00 |
| 1 | February 25 (Wed), 20:00-22:00 |
| 2 | March 2 (Mon), 15:00-19:00 |
| 2 | March 4 (Wed), 01:00-05:00 |
| 2 | March 6 (Fri), 20:00-00:00** |
| 3 | March 9 (Mon), 18:00-22:00 |
| 3 | March 13 (Fri), 12:00-16:00 |
*Times fall on the previous day in US Eastern time.
**Brownout extends to 00:00 UTC on March 7.
***Daylight Saving Time begins March 8, 2026. These dates use EDT (UTC-4).
Full enforcement begins March 16, 2026. At that time, all runner configurations/registrations from runners below v2.329.0 will be permanently blocked.
What you need to do
Update all self-hosted runners to v2.329.0 or later before configuration/registration by March 16, 2026:
- Download the latest runner release from the Actions Runner releases page.
- Update your installation scripts, images, or automation to install v2.329.0 or later before running
./config.sh. - Recreate or redeploy any runners built from images or templates that contain older versions.
- Review the upgrade documentation for detailed guidance.
For Actions Runner Controller (ARC) users:
– Ensure your runner container images include runner version v2.329.0 or later.
– Update any automation that builds or patches custom ARC runner images.
– If using official ARC runner images, pull recent versions that include the updated runner software.
To help avoid workflow disruptions, also ensure your self-hosted runners remain up to date according to the runner update policy described in the upgrade documentation