<?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 Pi Stack</title>
    <link>https://www.pistack.xyz/tags/versioning/</link>
    <description>Recent content in Versioning on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/versioning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Semantic Versioning Libraries in 2026: node-semver vs Masterminds vs python-semver</title>
      <link>https://www.pistack.xyz/posts/2026-09-27-semver-libraries-node-semver-masterminds-python-semver-comparison/</link>
      <pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-27-semver-libraries-node-semver-masterminds-python-semver-comparison/</guid>
      <description>&lt;p&gt;Your release pipeline just published a &amp;ldquo;patch&amp;rdquo; that silently deleted an API field. Nobody touched the code. What happened is that a comparator matched &lt;code&gt;2.0.0-rc.1&lt;/code&gt; against &lt;code&gt;&amp;gt;=1.0.0 &amp;lt;2.0.0&lt;/code&gt;, a resolver decided the release candidate was good enough, and the deploy bot rolled it out. Version comparison is one of those problems that looks like string manipulation and behaves like a parser spec: six mainstream ecosystems each implement it slightly differently, and the differences are exactly where production breaks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
