To continue executing workflow jobs: The runner must stay up to date by installing each new runner release within 30 days of its publication. This is an existing requirement but was not consistently enforced in some cases.
Souce: https://github.blog/changelog/2026-06-12-github-actions-minimum-version-enforcement-timeline-for-self-hosted-runners/
Perhaps we could semi-automate the update process by adding a script that can be run on a CI schedule, e.g. once a week, and checks for a new actions runner release and updates the version and hash and opens a PR. That would at least help reduce some of the churn, and help serve as a reminder to rebuild and redeploy.
affects both regular and ohos runners.
Souce: https://github.blog/changelog/2026-06-12-github-actions-minimum-version-enforcement-timeline-for-self-hosted-runners/
Perhaps we could semi-automate the update process by adding a script that can be run on a CI schedule, e.g. once a week, and checks for a new actions runner release and updates the version and hash and opens a PR. That would at least help reduce some of the churn, and help serve as a reminder to rebuild and redeploy.
affects both regular and ohos runners.