<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>REST API on Cloudkaramchari</title><link>https://www.cloudkaramchari.com/tags/rest-api/</link><description>Recent content in REST API on Cloudkaramchari</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>cloudkaramchari</copyright><lastBuildDate>Thu, 24 Sep 2026 09:00:00 +0530</lastBuildDate><atom:link href="https://www.cloudkaramchari.com/tags/rest-api/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub's New Runner Deprecation API: Automate Your Self-Hosted Fleet Audit</title><link>https://www.cloudkaramchari.com/blog/automate-github-actions-runner-deprecation-audits-with-the-new-rest-api/</link><pubDate>Thu, 24 Sep 2026 09:00:00 +0530</pubDate><guid>https://www.cloudkaramchari.com/blog/automate-github-actions-runner-deprecation-audits-with-the-new-rest-api/</guid><description>
&lt;h1 id="githubs-new-runner-deprecation-api-automate-your-self-hosted-fleet-audit">GitHub's New Runner Deprecation API: Automate Your Self-Hosted Fleet Audit&lt;/h1>
&lt;p>If you manage self-hosted GitHub Actions runners, you've probably already been checking versions by hand — SSH into a box, run &lt;code>./run.sh --version&lt;/code>, repeat for every machine. On September 3, 2026, GitHub shipped a REST API that makes that manual sweep unnecessary: &lt;code>GET /actions/runners/deprecations/{version}&lt;/code> returns the exact date a given runner version stops registering and the exact date it stops picking up jobs, for any version you ask about, at the repo, org, or enterprise level.&lt;/p></description></item></channel></rss>