GitHub moves Enterprise Cloud self-hosted runner enforcement to 29 September
GitHub says full enforcement of its self-hosted-runner minimum-version requirements for GitHub Enterprise Cloud starts on 29 September 2026, replacing an unspecified earlier date. The company says runners below 2.329.0 will not be able to register or reregister, and runners below a higher undisclosed runtime minimum will stop executing jobs.[1]
This edition passed Imananq's enhanced publication checks. Some material claims remain explicitly attributed to official or company sources because no independent source is currently bound to this edition. The engine continues checking approved sources and will add corroboration only through a new edition that passes the full gate.
GitHub has moved full enforcement of minimum-version requirements for self-hosted GitHub Actions runners on GitHub Enterprise Cloud to 29 September 2026. GitHub says the requirements themselves have not changed: runners below version 2.329.0 cannot register or reregister, while already registered runners below a separate, higher runtime minimum will cease running workflow jobs.[1]
01
What we know now
- 01
[1] GitHub Changelog, "Self-hosted runner version enforcement date has moved," primary notice: https://github.blog/changelog/2026-09-28-self-hosted-runner-version-enforcement-date-has-moved.
- 02
GitHub's account is first-party product information; the runtime minimum version and API access details are not provided in the acquired notice.
02
Full enforcement for GitHub Enterprise Cloud begins
GitHub says the revised full-enforcement date is 29 September 2026.Registration and reregistration threshold
Runners below this version will be unable to register or reregister, according to GitHub.Enterprise Cloud with Data Residency enforcement
GitHub records that enforcement for this offering began on 31 July 2026.Dates and version threshold are first-party GitHub statements.[1]
03
Revised schedule
GitHub announced a revised enforcement schedule for the minimum versions of self-hosted GitHub Actions runners on GitHub Enterprise Cloud. The company says full enforcement begins the following day, 29 September 2026. The notice describes this as a date change rather than a change to the underlying requirements.[1]
- Full enforcement now begins on 29 September 2026; GitHub says this replaces a previously announced date, which the notice does not identify.
- The schedule change was shipped on 28 September 2026, according to GitHub.
04
Operational effect
GitHub distinguishes between registration and job execution. Its stated 2.329.0 threshold applies to registering or reregistering a self-hosted runner. A different minimum applies when executing workflow jobs; GitHub says it is higher, but does not disclose the version in this notice. That means an already registered runner can still face job disruption if it is below the runtime requirement.[1]
- Below 2.329.0: runners cannot register or reregister.
- Below the undisclosed, higher runtime minimum: existing runners stop executing workflow jobs.
- The runtime threshold is distinct from, and higher than, the registration threshold.
05
Scope of the change
The announcement limits the shifted schedule to GitHub Enterprise Cloud. GitHub explicitly says GitHub Enterprise Server is not impacted. It also records that enforcement had already begun for GitHub Enterprise Cloud with Data Residency on 31 July 2026.[1]
- The revised date affects GitHub Enterprise Cloud.
- GitHub Enterprise Server is not affected by this change.
- GitHub says enforcement for GitHub Enterprise Cloud with Data Residency began on 31 July 2026.
06
What administrators can do
GitHub advises affected Enterprise Cloud users to upgrade self-hosted runners before full enforcement begins and to review version-deprecation dates for their fleets.[1]
- 01
Check whether any self-hosted runner is below version 2.329.0, the stated registration and reregistration threshold.[1]
- 02
Identify runners that are below GitHub's separate, higher runtime minimum, because these may stop executing workflow jobs even if already registered.[1]
- 03
Use GitHub's runner-version-deprecations REST API to review registration and runtime deadlines and automate fleet alerts. The acquired notice does not specify the endpoint or required permissions.[1]
- 04
Confirm the deployment type: GitHub says this schedule change applies to GitHub Enterprise Cloud, not GitHub Enterprise Server.[1]
07
Limits of this edition
GitHub's notice does not state the earlier enforcement date that was replaced.[1]
The notice does not give the higher runner version required for workflow-job execution.[1]
The acquired evidence does not include the REST API endpoint, authentication or permissions requirements, or the linked upgrade-guidance URL.[1]
SRC
Source desk
Direct links to the material behind this selection. Seeing the source matters as much as reading the synthesis.
Keep exploring
27 Sept 2026
Rolling-WAM preprint proposes rolling denoising for faster robot replanning
Rolling-WAM is an under-review preprint whose authors propose carrying partially denoised video-action chunks across replanning cycles. They report competitive manipulation performance in named evaluations and a 4.5x steady-state replanning speedup over standard joint WAMs, but the supplied primary record does not provide enough detail for independent assessment.
7 Sept 2026
Google announces agentic video understanding for Gemini API
Google says agentic video understanding is available through its Gemini API for three Flash models and can be enabled with an "agentic" processing setting. Google reports lower token use and costs and higher accuracy, and names LongVideoBench for one comparison, but does not provide the full benchmark methodology or conditions. It also says a Gemini app rollout will reach all users on Flash and Flash-Lite models soon, without a date or regional scope. [1]
27 Sept 2026
RAPID proposes turning one visual human demonstration into a testable program
RAPID is an arXiv preprint whose authors propose automatically creating, testing, and refining robot programs from a single visual human demonstration. They report simulation and real-robot evaluations, including eight nonprehensile tasks, but the supplied record lacks metrics, baselines, peer review, replication, and detailed deployment constraints.