<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Turya Kalburgi</title>
    <description>The latest articles on DEV Community by Turya Kalburgi (@turyakalburgi).</description>
    <link>https://dev.to/turyakalburgi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4129634%2Fd5a66be3-cff7-4d22-89ef-7acbcb6460fb.png</url>
      <title>DEV Community: Turya Kalburgi</title>
      <link>https://dev.to/turyakalburgi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/turyakalburgi"/>
    <language>en</language>
    <item>
      <title>How I built a lightweight GitHub Action to stop breaking API changes in CI</title>
      <dc:creator>Turya Kalburgi</dc:creator>
      <pubDate>Thu, 17 Sep 2026 10:20:32 +0000</pubDate>
      <link>https://dev.to/turyakalburgi/how-i-built-a-lightweight-github-action-to-stop-breaking-api-changes-in-ci-3jam</link>
      <guid>https://dev.to/turyakalburgi/how-i-built-a-lightweight-github-action-to-stop-breaking-api-changes-in-ci-3jam</guid>
      <description>&lt;p&gt;Breaking API contracts silently slipping into production is a pain point almost every engineering team hits eventually. A backend PR renames a field, drops a property, or mutates a type—and downstream services or frontends immediately break.&lt;/p&gt;

&lt;p&gt;To catch this before merges happen, I built &lt;strong&gt;API Drift Sentinel&lt;/strong&gt;—a zero-config GitHub Action that detects breaking OpenAPI/Swagger schema changes directly in your PR workflows.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why not existing tools?
&lt;/h3&gt;

&lt;p&gt;Most existing solutions either require heavy external cloud platforms or demand installing full Node/Python runtimes during the CI run. &lt;/p&gt;

&lt;p&gt;I wanted something drop-in and ultra-fast:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Zero config:&lt;/strong&gt; Works out of the box for standard OpenAPI 3.0 / Swagger specs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fail-fast:&lt;/strong&gt; Exits with code &lt;code&gt;1&lt;/code&gt; and emits inline GitHub PR annotations whenever breaking changes are caught.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pre-bundled with esbuild:&lt;/strong&gt; Bundled down to a standalone script, running in ~50ms without an &lt;code&gt;npm install&lt;/code&gt; step on your runner.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  How to use it
&lt;/h3&gt;

&lt;p&gt;Add this step to your GitHub Actions workflow (e.g., &lt;code&gt;.github/workflows/ci.yml&lt;/code&gt;):&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
yaml
- name: Check for Breaking API Changes
  uses: Turya-Kalburgi/api-drift-sentinel@v1
  with:
    base-spec: 'openapi.yaml'


&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>devops</category>
      <category>webdev</category>
      <category>opensource</category>
      <category>github</category>
    </item>
  </channel>
</rss>
