← Back
GitHub
GitHub pauses self-hosted runner minimum version enforcement
GitHub Actions · releaseapideprecation · github.blog ↗

Enforcement Pause

GitHub has paused the enforcement of the minimum self-hosted runner version requirement (v2.329.0) that was originally scheduled to take effect on March 16, 2026. This means runners below v2.329.0 can still register and configure during this interim period without being blocked.

What This Means for Users

The enforcement pause applies specifically to configuration and registration time (when running ./config.sh to register a new runner), not to the execution of workflows by already-registered runners. GitHub will continue to reject runners older than the latest release by more than 30 days (currently v2.330.0 and below) as part of its standard deprecation process.

Important notes:

  • Runners with auto-update disabled (including those managed by ARC with disableUpdate=true) must still be manually updated to a supported version
  • GitHub Enterprise Server (GHES) customers are not impacted by this change
  • This pause does not change GitHub's long-term direction to eventually block older runner versions

What You Should Do

GitHub strongly encourages all users to continue upgrading self-hosted runners to v2.329.0 or later as soon as possible. An updated enforcement timeline and plan will be published in the coming weeks. Refer to the upgrade documentation for detailed guidance on upgrading your runners.