Semantic Versioning (SemVer)

Question 1

What does the ‘MAJOR’ version number in Semantic Versioning indicate?

Answer 1

Incompatible API changes or breaking changes that might require users to adjust their code.

Question 2

The version format in Semantic Versioning is ___.

Answer 2

MAJOR.MINOR.PATCH

Question 3

True or False: A ‘MINOR’ version change indicates a backward-compatible bug fix.

Answer 3

False

Question 4

How does Semantic Versioning benefit developers when updating software dependencies?

Answer 4

It provides clarity, compatibility, and predictability about updates, making it easier to manage dependencies and make updates confidently.

Question 5

Fill in the blank: A backward-compatible bug fix would result in a change in the ______ version number.

Answer 5

PATCH

Question 6

Compare a ‘MAJOR’ version change to a ‘MINOR’ version change in Semantic Versioning.

Answer 6

A ‘MAJOR’ version change involves breaking changes that may affect compatibility, while a ‘MINOR’ version change adds new features in a backward-compatible way.

Question 7

What version number would come after 1.3.5 if a new feature is added without breaking compatibility?

Answer 7

1.4.0

Question 8

True or False: The Semantic Versioning format allows for additional identifiers for pre-release versions and build metadata.

Answer 8

True

Question 9

What is the purpose of the ‘PATCH’ version in Semantic Versioning?

Answer 9

To indicate backward-compatible bug fixes or minor changes that don’t impact functionality.

Question 10

Provide an example of a Semantic Versioning number with build metadata.

Answer 10

1.0.0+20130313144700

Question 11

In Semantic Versioning, what does a version change from 2.0.1 to 2.0.2 imply?

Answer 11

A minor bug fix or small change that is backward-compatible.

Question 12

How would you label a pre-release version in Semantic Versioning? Give an example.

Answer 12

By adding an identifier like ‘-alpha’ or ‘-beta’; e.g., 1.0.0-alpha.

Question 13

What happens when a MINOR version is updated?

Answer 13

A new feature is added in a backward-compatible way, meaning existing code doesn’t need to change.

Question 14

Explain what the ‘2’ represents in version 2.3.4 under Semantic Versioning.

Answer 14

The MAJOR version, which indicates breaking changes that may require users to adjust their code.

Question 15

In Semantic Versioning, what would you expect from a release labeled as 3.2.0?

Answer 15

New functionality added in a backward-compatible way, as it’s a MINOR update.

Question 16

True or False: A change from version 1.0.0 to 1.0.1 could include breaking changes.

Answer 16

False

Question 17

Describe a situation where you might need to update the MAJOR version number.

Answer 17

When making a change that is incompatible with previous versions, potentially breaking existing code for users.

Question 18

How does Semantic Versioning improve compatibility management in software projects?

Answer 18

It lets users understand the impact of updates, especially for libraries and APIs, by indicating breaking changes, new features, or fixes.

Question 19

True or False: The MINOR version number should increase when only bug fixes are implemented.

Answer 19

False

Question 20

Fill in the blank: A new feature added in a backward-compatible manner would update the ______ version.

Answer 20

MINOR