Semantic Versioning: A Quick Guide


In the field of software and application development, version numbers are used to track releases. If this needs to be done, it must be done in a standardized and consistent manner to prevent conflicts.

Semantic Versioning

Semantic versioning is a method of versioning software, software packages, or libraries in a logical manner. This versioning is done by assigning a version number (a decimal number) to the so-called software. With the presence of two decimal points, a version number can be further divided into three: a major version number, a minor version number, and a patch version number, respectively.

Major Version

This version number is updated (incremented) whenever an API or piece of software receives updates that render the prior version obsolete. Things won't function the same way they did before when there is a significant change, which can also lead to incompatibilities.

A software or API user can get ready for glaring changes in terms of software and breaking changes in terms of APIs with a conspicuous change in a major version number.

 

 

Minor Version

The reason for changing (incrementing) this version number is almost identical to that of the major version. With minor modifications to an API or software, things won’t function the way they did before, but this is not a breaking change; rather, it is an addition of functionality to the existing API or software.

 

Patch Version

In order to improve APIs or software, we fix bugs, correct programming errors, and make other adjustments. The patch version should be changed at this point if possible.

Post a Comment

Previous Post Next Post