What does semantic versioning communicate?

What does semantic versioning communicate?

• A. The release date
• B. Changes in major/minor/patch levels to indicate compatibility and changes
• C. The programming language
• D. The number of commits

Answer: (B)

Semantic versioning communicates the scope and compatibility of changes using a three-part version number (major.minor.patch). The major version increases when there are incompatible API changes, signaling that code depending on the previous API may need changes. The minor version increases when new, backwards-compatible functionality is added, letting users upgrade to get new features without breaking existing code. The patch version increases for backwards-compatible bug fixes and minor improvements, providing a safe upgrade path for fixes. This system helps developers and package managers decide how risky an upgrade is and how to manage dependencies. It does not convey release dates, programming languages, or the number of commits.

Semantic versioning communicates the scope and compatibility of changes using a three-part version number (major.minor.patch). The major version increases when there are incompatible API changes, signaling that code depending on the previous API may need changes. The minor version increases when new, backwards-compatible functionality is added, letting users upgrade to get new features without breaking existing code. The patch version increases for backwards-compatible bug fixes and minor improvements, providing a safe upgrade path for fixes. This system helps developers and package managers decide how risky an upgrade is and how to manage dependencies. It does not convey release dates, programming languages, or the number of commits.