<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Semver on Omar Crosby</title>
    <link>https://omarcrosby.com/tags/semver/</link>
    <description>Recent content in Semver on Omar Crosby</description>
    <image>
      <title>Omar Crosby</title>
      <url>https://omarcrosby.com/images/og.jpg</url>
      <link>https://omarcrosby.com/images/og.jpg</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 20 Jul 2026 09:40:46 -0400</lastBuildDate>
    <atom:link href="https://omarcrosby.com/tags/semver/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Semantic Versioning, Semantic Release, and a Go-native implementation</title>
      <link>https://omarcrosby.com/posts/semantic-versioning-semantic-release-and-a-go-native-implementation/</link>
      <pubDate>Mon, 20 Jul 2026 09:40:46 -0400</pubDate>
      <guid>https://omarcrosby.com/posts/semantic-versioning-semantic-release-and-a-go-native-implementation/</guid>
      <description>How Semantic Versioning and Semantic Release fit together — the standard, the automation contract that turns commit history into version tags, and why I re-implemented the Node.js tool in Go to remove the JavaScript toolchain from CI pipelines that don&amp;#39;t otherwise need one.</description>
    </item>
  </channel>
</rss>
