Скачать или смотреть Understanding Semantic Versioning

Semantic Versioning (SemVer)

Semantic Versioning is a versioning system used to label software releases in a way that conveys meaning about the underlying changes. It follows the format:

MAJOR.MINOR.PATCH

Each component has a specific purpose:

1. Components of Semantic Versioning

MAJOR (Breaking Changes):
Incremented when there are incompatible changes that require modifications by users to upgrade.
Example: 1.0.0 → 2.0.0

MINOR (New Features):
Incremented when new, backward-compatible functionality is introduced.
Example: 1.0.0 → 1.1.0

PATCH (Bug Fixes):
Incremented when backward-compatible bug fixes are made.
Example: 1.0.0 → 1.0.1

2. Pre-release Versions

Optional pre-release labels can indicate unstable or development versions before a final release.
Format: MAJOR.MINOR.PATCH-pre-release
Example: 1.0.0-alpha, 1.0.0-beta.1, 1.0.0-rc.1

3. Build Metadata

Build metadata can indicate additional information, such as build numbers or environment details.
Format: MAJOR.MINOR.PATCH+build-metadata
Example: 1.0.0+20231225

4. Benefits of Semantic Versioning

Clarity: Communicates the scope and impact of changes.

Predictability: Helps developers and users understand upgrade implications.

Compatibility: Encourages backward-compatible changes for seamless upgrades.

Standardization: Promotes a common versioning language across projects.

5. Example Scenarios

1.2.3 → 2.0.0: Major version change due to breaking changes.

1.2.3 → 1.3.0: Minor version change due to added functionality.

1.2.3 → 1.2.4: Patch version change due to a bug fix.

Semantic Versioning is widely used in software development to manage version control, maintain compatibility, and set clear expectations for users.