<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Breaking-Changes on christos gkoros</title>
    <link>https://christosgkoros.com/tags/breaking-changes/</link>
    <description>Recent content in Breaking-Changes on christos gkoros</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 06 Aug 2026 08:00:00 +0300</lastBuildDate>
    <atom:link href="https://christosgkoros.com/tags/breaking-changes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Breaking Changes in HTTP APIs</title>
      <link>https://christosgkoros.com/posts/2026/08/06/breaking-changes-in-http-apis/</link>
      <pubDate>Thu, 06 Aug 2026 08:00:00 +0300</pubDate>
      <guid>https://christosgkoros.com/posts/2026/08/06/breaking-changes-in-http-apis/</guid>
      <description>A change is breaking if a client that worked yesterday has to change its code, its configuration, or its infrastructure to keep working today. That includes changes that keep every client running while quietly giving it wrong data — those are still breaking, only harder to notice.&#xA;Most of the list below follows from one rule. On the request side, anything that narrows what the API accepts is breaking, because traffic that was valid yesterday must stay valid.</description>
    </item>
  </channel>
</rss>
