GitHub Actions 自托管 Runner 版本强制生效日期推迟至 2026-09-29
Self-hosted runner version enforcement date has moved
CI/CD 流水线重度用户注意：GitHub 自托管 Runner 版本强制执行的最后期限已更新为 9 月 29 日。请立刻核查 fleet 中低于 v2.329.0 的节点，避免届时因无法注册或停止运行导致构建中断。
The enforcement date for GitHub Actions minimum version requirements for self-hosted runners on GitHub Enterprise Cloud has changed. The change ships Monday, September 28, 2026, and full enforcement now begins Tuesday, September 29, 2026. This is instead of the date that was previously announced.
GitHub Enterprise Cloud 上自托管运行器的 GitHub Actions 最低版本要求的执行日期已更改。该变更将于 2026 年 9 月 28 日（星期一）生效，全面执行现从 2026 年 9 月 29 日（星期二）开始。这与此前公布的日期不同。
The requirements themselves are unchanged:
要求本身并未改变：
- Self-hosted runners below version 2.329.0 won’t be able to register or reregister.
- Existing runners below the minimum version required to execute workflow jobs (which is a higher version than the registration minimum) will stop running jobs, even if they were previously registered.
- 版本低于 2.329.0 的自托管运行器将无法注册或重新注册。
- 低于执行工作流作业所需最低版本（该版本高于注册最低版本）的现有运行器将停止运行作业，即使它们之前已注册。
If you haven’t upgraded your self-hosted runners yet, do so before September 29, 2026 to avoid disruption to your workflows. See the self-hosted runner documentation for upgrade guidance. You can also use the new REST API for runner version deprecations to check the registration and runtime deprecation dates for any runner version and build automated alerts for fleets nearing their deadline.
如果您尚未升级自托管运行器，请在 2026 年 9 月 29 日之前完成升级，以避免影响您的工作流。请参阅自托管运行器文档以获取升级指南。您还可以使用新的 REST API 来查询运行器版本弃用情况，检查任何运行器版本的注册和运行时弃用日期，并为即将达到截止期限的运行器集群构建自动化警报。
This shift only affects GitHub Enterprise Cloud. GitHub Enterprise Server isn’t impacted. Enforcement already began for GitHub Enterprise Cloud with Data Residency on July 31, 2026.
此次调整仅影响 GitHub Enterprise Cloud。GitHub Enterprise Server 不受影响。针对带有数据驻留功能的 GitHub Enterprise Cloud，执行已于 2026 年 7 月 31 日开始。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力