This system uses a set of three numbers like 1.2.3 to track software updates. Each position represents a different level of change, from big to small.

The Three Numbers

The first number changes when there are big updates that aren't compatible with older versions. This signals that users might need to change how they use the software.

The Major Version

The second number increases when new features are added. These updates are safe to install because they don't break existing parts of the program.

The Minor Version

The third number goes up for tiny changes, like fixing a mistake or a bug. These are the safest updates and don't add any new functionality.

The Patch Version

This is often called backward compatibility. It means the new version can still understand and work with instructions written for the old version.

Working with Older Versions

A breaking change happens when an update removes or changes a feature that other programs rely on. This requires increasing the major version number.

Breaking the Rules

Software often starts at version 0.x.x while it is still being built. In this stage, things change very fast and the rules are more flexible.

The Development Phase

Reaching version 1.0.0 is a big milestone. It tells everyone that the software is officially ready for daily use and will follow strict versioning rules.

The First Stable Version

When a higher number increases, the numbers to its right reset to zero. For example, moving from version 1.5.2 to 2.0.0 clears the smaller change counts.

Resetting the Count

Sometimes a label like 'alpha' or 'beta' is added to the end of a version. This warns users that the software is a work-in-progress and might have bugs.

Early Test Versions

To use this system, a project must clearly define its 'API,' which is just the list of rules for how other software can talk to it.

Public Rules of Interaction

Clear version numbers help prevent 'dependency hell.' This happens when different pieces of software can't work together because their versions clash.

Avoiding Update Nightmares

Modern tools can automatically figure out which number to increase based on the notes a developer writes. This keeps the naming process consistent and fair.

Automatic Version Management

By looking at the version numbers, users can decide if an update is safe to install immediately or if they should test it first.

Choosing When to Update

Version numbers act like a language for developers. They tell a story about the software’s history without needing to read pages of notes.

What is a Breaking Change?