<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Hosted Runners on Cloudkaramchari</title><link>https://www.cloudkaramchari.com/tags/self-hosted-runners/</link><description>Recent content in Self-Hosted Runners on Cloudkaramchari</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>cloudkaramchari</copyright><lastBuildDate>Sat, 29 Aug 2026 11:00:00 +0530</lastBuildDate><atom:link href="https://www.cloudkaramchari.com/tags/self-hosted-runners/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Actions Self-Hosted Runners: Fix Your Version Before the September 25 Enforcement</title><link>https://www.cloudkaramchari.com/blog/github-actions-self-hosted-runner-version-enforcement-brownouts-september-2026/</link><pubDate>Sat, 29 Aug 2026 11:00:00 +0530</pubDate><guid>https://www.cloudkaramchari.com/blog/github-actions-self-hosted-runner-version-enforcement-brownouts-september-2026/</guid><description>
&lt;h1 id="github-actions-self-hosted-runners-fix-your-version-before-the-september-25-enforcement">GitHub Actions Self-Hosted Runners: Fix Your Version Before the September 25 Enforcement&lt;/h1>
&lt;p>If your CI/CD pipeline runs on self-hosted GitHub Actions runners, GitHub has already started intermittently blocking outdated ones. Brownouts began August 24, 2026 on github.com and GitHub Enterprise Cloud, and they escalate on a fixed schedule until full enforcement locks out unsupported runners permanently on September 25, 2026. This isn't a future warning — it's already happening, on and off, for four hours a day, and the blocked window gets wider and more frequent each week.&lt;/p></description></item></channel></rss>