Skip to main content

Semantic Versioning (SemVer) Explained for Absolute Dummies

Image
By mvryo
Photo by Austris Augusts on Unsplash


If you’ve seen version numbers like 1.2.3 or 4.5.6-beta, and wondered what all those numbers mean — you're in the right place.

This is your no-jargon, easy-to-digest guide to Semantic Versioning — or SemVer.

What is Semantic Versioning?

Semantic Versioning is a standard for naming versions of your software. It uses three numbers:

MAJOR.MINOR.PATCH

Basic Format

1.2.3
↑ ↑ ↑
│ │ └─ PATCH
│ └─── MINOR
└───── MAJOR

Now let’s break it down — as if you’re explaining it to your non-techy cousin.

The Numbers

1. MAJOR version (1.x.x)

  • When you break things.
  • Not compatible with old versions.
  • You remove or change a function’s behavior in a way that older code will break.

Example:
You go from 1.2.3 ➜ 2.0.0
"Whoa, we broke something!"

2. MINOR version (x.1.x)

  • When you add features, but nothing breaks.
  • Compatible with old versions.

Example:
You go from 1.2.3 ➜ 1.3.0
"Hey, we added something new, but old stuff still works!"

3. PATCH version (x.x.3)

  • When you fix bugs or make tiny changes.
  • No new features. Just repairs.

Example:
You go from 1.2.3 ➜ 1.2.4
"Oops, we squashed a bug!"

Pre-release Tags (Optional)

Sometimes you’re not ready to release a final version. So you tag it:

  • 1.0.0-alpha — very early preview
  • 1.0.0-beta — almost ready, still testing
  • 1.0.0-rc.1 — release candidate (final test)

Build Metadata

You can add extra info after a +, like a date or commit hash.

Example:

1.0.0+20240618

This doesn’t affect how it’s compared to other versions. It’s just info.

Real-World Examples

  • Fixed a small typo 1.0.0 ➜ 1.0.1
  • Added new feature (non-breaking) 1.0.1 ➜ 1.1.0
  • Removed a function (breaking change) 1.1.0 ➜ 2.0.0
  • Released test version for feedback 2.0.0 ➜ 2.0.0-beta

Cheat Sheet for Dummies

  • Bug fix = PATCH
  • New feature = MINOR
  • Breaking change = MAJOR
  • Not final version = Add suffix like -beta, -rc.1

Conclusion

  • Don’t just change 1.0.0 to 5.0.0 because it looks cooler. Stick to meaning!
  • Semantic Versioning helps users, developers, and tools understand how big the change is.
  • You’re not just naming a version — you’re setting expectations.

Now go and bump that version like a pro.

TL;DR

Semantic Versioning is just a smart way to say:
“Did we fix a bug? Add a feature? Or break something?”

Labels:

Comments

Post a Comment

Popular posts from this blog

Understanding Number Systems: Decimal, Binary, and Hexadecimal

By mvryo
In everyday life, we use numbers all the time, whether for counting, telling time, or handling money. The number system we’re most familiar with is the   decimal system , but computers use other systems, such as   binary   and   hexadecimal . Let’s break down these number systems to understand how they work. What is a Number System? A number system is a way of representing numbers using a set of symbols and rules. The most common number systems are: Decimal (Base 10) Binary (Base 2) Hexadecimal (Base 16) Each system has a different “base” that tells us how many unique digits (symbols) are used to represent numbers. Decimal Number System (Base 10) This is the system we use daily. It has  10 digits , ranging from  0 to 9 . Example: The number  529  in decimal means: 5 × 1⁰² + 2 × 1⁰¹ + 9 × 1⁰⁰ =  500 + 20 + 9 = 529 Each position represents a power of 10, starting from the rightmost digit. Why Base 10? Decimal is base 10 because it has 10 digits...
Post a Comment
Read More »

How to Monetize Your API as an Individual Developer While Hosting on Your Own Server?

By mvryo
In the API economy, cloud services like AWS, Google Cloud, and Azure offer many conveniences, such as scaling and infrastructure management. However, some developers prefer more control and autonomy, opting to host their APIs on personal servers. Whether for cost efficiency, data privacy, or customization, hosting your own API comes with both advantages and challenges. But, even without cloud platforms, there are effective ways to monetize your API. This guide will explore how individual developers can successfully monetize their APIs while hosting them on their own servers. Why Host Your API on Your Own Server? Hosting your own API gives you full control over the infrastructure and potentially lower long-term costs. Here’s why some developers choose this approach: Cost Control : Instead of paying ongoing cloud fees, you may opt for a one-time or lower-cost hosting solution that fits your budget and resource needs. Data Ownership : You have full control over data, which is critical if ...
Post a Comment
Read More »

The Weight of Responsibility: A Developer’s Journey to Balance Passion and Reality

By mvryo
For the past several years, Eddie has been on a steady climb in his career as a developer, but recently, he found himself at a crossroads — caught between the weight of his responsibilities and the desire to pursue his true passions. His journey began with a three-month internship as a web developer, which led to nearly four years in an application developer role. After that, he spent almost a year as a systems associate, managing tasks across systems analysis, quality assurance, and business analysis. Eventually, he returned to full-time software development for another two years before transitioning into more complex roles. For over a year, he worked as a multi-role software developer and database administrator before stepping into his current position as a senior software developer, database administrator, and cloud administrator — occasionally handling security tasks as well. Now, with over 8 years of professional experience, he also leads a small team of developers, which has been...
Post a Comment
Read More »

The Hidden Costs of Overdesign and Bad Practices in API Systems

By mvryo
In software development, simplicity and clarity are often sacrificed in favor of overly complex solutions. While it can be tempting to add more features and intricate designs to ensure robustness, overdesign and poor practices can have significant consequences. They frustrate developers, lead to inefficiencies, increase costs, and put unnecessary strain on system resources.  A recent example involving a team that has faced challenges with complexity highlights the pitfalls of such an approach. Overdesign: The Problem of Too Much Complexity Overdesign occurs when systems are built with more complexity than necessary. This might manifest in bloated APIs, convoluted data flows, or excessive checks and processes that don’t add substantial value. The goal is often to anticipate future problems, but this approach typically results in cumbersome systems that are difficult to maintain and scale. In one case, a company found itself paying a hefty price just to host two API services and a po...
Post a Comment
Read More »

Selenium for Beginners: What, Where, When, and Why to Use It in Automated Testing

By mvryo
In today’s software development landscape, automated testing has become essential for delivering robust applications efficiently. Among various automated testing tools,   Selenium   stands out as one of the most widely used and beginner-friendly options. As you embark on your journey into automated testing, it’s crucial to understand the   what, where, when, and why   of using Selenium. In this guide we will run through these essentials and help you decide if Selenium is the right tool for you. What is Selenium? Selenium  is an open-source framework used primarily for automating web browsers. It enables developers and testers to write scripts that interact with websites, simulating actions like clicking buttons, filling out forms, and navigating pages, which allows for comprehensive automated testing. Selenium supports multiple programming languages, including Python, Java, C#, and JavaScript, making it flexible for teams with different coding preferences. Key C...
Post a Comment
Read More »