<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Versioning on Nalar</title>
    <link>https://nalar.dev/tags/versioning/</link>
    <description>Recent content in Versioning on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/versioning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Versioning Contracts, Not Just Releases</title>
      <link>https://nalar.dev/versioning-contracts-not-just-releases/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/versioning-contracts-not-just-releases/</guid>
      <description>&lt;p&gt;A version number is useful only when its consumers can make a decision from it.&lt;/p&gt;&#xA;&lt;p&gt;Suppose a library changes from &lt;code&gt;2.4.1&lt;/code&gt; to &lt;code&gt;2.5.0&lt;/code&gt;. A developer considering the upgrade wants to know something practical: can existing code keep working, or must it change? The answer does not come from how much code the maintainer edited. It comes from whether the release changed a &lt;strong&gt;contract that consumers depend on&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;That contract includes more than function names. It can include accepted inputs, returned values, error behavior, configuration, file formats, command-line options, extension points, and other observable behavior that the project promises to preserve.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
