<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Semantic Versioning</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Semantic Versioning feed</description>
    <item>
      <title>Article: Beyond API Compatibility: Understanding the Full Impact of Breaking Changes</title>
      <link>https://www.infoq.com/articles/breaking-changes-are-broken-semver/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Semantic+Versioning</link>
      <description>&lt;img src="https://res.infoq.com/articles/breaking-changes-are-broken-semver/en/headerimage/breaking-changes-are-broken-header-1705413989390.jpg"/&gt;&lt;p&gt;In this article, we address the most contentious and misinterpreted parts of the SemVer standard, i.e  backward compatibility and breaking changes. With the proliferation of SaaS APIs for Generative AI continuing, now is a good time for a retrospection on what constitutes a breaking change and how you can trade off backward compatibility and upgradability with modernization and iterability.&lt;/p&gt; &lt;i&gt;By Ashwin Raghav Mohan Ganesh&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>SaaS</category>
      <category>Semantic Versioning</category>
      <category>Release Management</category>
      <category>API</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Thu, 18 Jan 2024 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/breaking-changes-are-broken-semver/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Semantic+Versioning</guid>
      <dc:creator>Ashwin Raghav Mohan Ganesh</dc:creator>
      <dc:date>2024-01-18T09:00:00Z</dc:date>
      <dc:identifier>/articles/breaking-changes-are-broken-semver/en</dc:identifier>
    </item>
  </channel>
</rss>
