<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Model Deprecation on No Semicolons</title><link>https://nosemicolons.com/tags/model-deprecation/</link><description>Recent content in Model Deprecation on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 16:38:45 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/model-deprecation/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Retirement Crisis: How to Future-Proof Your Codebase When Your Favorite Model Gets Deprecated</title><link>https://nosemicolons.com/posts/ai-code-generation-model-retirement-crisis-future-proof-codebase/</link><pubDate>Mon, 05 Oct 2026 16:38:45 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-model-retirement-crisis-future-proof-codebase/</guid><description>&lt;p>Remember when GitHub deprecated their Code Search API with just six months notice? If you built your entire workflow around it, you probably felt that familiar sinking feeling. Now imagine that happening with the AI model that&amp;rsquo;s been your coding companion for months.&lt;/p>
&lt;p>We&amp;rsquo;re heading into what I&amp;rsquo;m calling the &amp;ldquo;AI Model Retirement Crisis.&amp;rdquo; As AI companies iterate rapidly, models get deprecated, pricing changes overnight, and your favorite coding assistant might vanish faster than you can say &amp;ldquo;breaking change.&amp;rdquo; I learned this the hard way when a client&amp;rsquo;s entire code review automation broke because they&amp;rsquo;d hardcoded everything around a specific model&amp;rsquo;s output format.&lt;/p></description></item></channel></rss>