Minorversjonen

Minorversjonen, or the minor version, is a term used in software versioning to denote a specific class of release. It represents the second component in common three-part version schemes such as MAJOR.MINOR.PATCH. A minor version typically signals backward‑compatible changes that add functionality or improvements, without breaking existing public interfaces.

In semantic versioning (SemVer), increments to the minor component indicate that new features or enhancements have been introduced in a way that remains backward compatible. This means existing code that depends on the previous minor version should continue to work, though users may gain access to new capabilities. The patch component is reserved for bug fixes and minor fixes that do not affect behavior, while the major component signals potentially breaking changes.

Examples help illustrate the concept: upgrading from 1.2.3 to 1.3.0 adds features without removing compatibility, and upgrading from 2.0.0 to 2.1.0 similarly introduces new functionality in a non-breaking way.

The minor version has practical significance for developers and consumers. Dependency management systems often use the minor version as a cue for compatibility and update policies. A shift from 1.x to 2.x is usually treated as a larger change, but a move within the same minor line (e.g., 1.4.0 to 1.4.1) is typically viewed as safe for automated updates.

Not all projects follow SemVer; some use date-based CalVer or other schemes. Nevertheless, the concept of the minor version remains a common way to communicate backward-compatible enhancements to users.