<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Semver on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/semver/</link><description>Recent content in Semver on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 26 Mar 2026 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/semver/index.xml" rel="self" type="application/rss+xml"/><item><title>Semantic Versioning done automatically</title><link>https://javapro-en.svenruppert.com/semantic-versioning-done-automatically/</link><pubDate>Thu, 26 Mar 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/semantic-versioning-done-automatically/</guid><description>&lt;p&gt;Software evolves over time. Bugs are fixed, features are added, and occasionally design mistakes are corrected in ways that are incompatible with earlier releases. Version numbers exist to identify these distinct states of a software artifact and to allow consumers to reason about whether an upgrade is safe. Without versioning, it is impossible to distinguish between two builds of the same library or to express expectations about their compatibility.&lt;/p&gt;
&lt;h2 id="semantic-versioning"&gt;Semantic Versioning&lt;/h2&gt;
&lt;p&gt;Software versions come in many forms, ranging from simple incrementing numbers to schemes based on release dates. One of the most widely adopted approaches is Semantic Versioning, commonly abbreviated as SemVer. SemVer defines a structured MAJOR.MINOR.PATCH version format with explicit rules about how version numbers must change in response to different kinds of software changes.&lt;/p&gt;</description></item></channel></rss>