Editor’s note (March 17, 2026): We updated this post to clarify that the v2.329.0 minimum version enforcement that has been paused applies only at configuration/registration time (i.e., when running ./config.sh to register a new runner), and does not determine the minimum version required for already-registered runners to pick up and execute workflows. Separately, runners on versions older than the latest release by more than 30 days (currently v2.330.0 and below) will be rejected from executing workflows as part of our standard runner deprecation process. Runners with auto-update disabled (including those managed by ARC with disableUpdate=true) must be manually updated to a supported version. GitHub Enterprise Server (GHES) customers are not impacted by this change.

We’re temporarily pausing GitHub Actions enforcement of the minimum self-hosted runner version requirement (v2.329.0) scheduled to take effect on March 16, 2026. Runners below v2.329.0 can still register and configure during this period.

We’ll publish an updated timeline and enforcement plan in the coming weeks. We strongly encourage you to continue upgrading your self-hosted runners to v2.329.0 or later as soon as you can (review the upgrade documentation for detailed guidance).

This doesn’t change our long-term direction. We still plan to block older runner versions from registration and configuration. We’re taking this time to ensure a smooth transition.

For reference, here are the previous communications on this topic:

Learn more in our documentation about self-hosted runner management.