Semantic versioning with tags in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Identify the output of a semantic version tag listing command

You run the command git tag --list 'v1.*' in a repository with these tags: v1.0.0, v1.2.3, v2.0.0, v1.10.0. What is the output?

Git

git tag --list 'v1.*'

A

v1.0.0
v1.10.0
v1.2.3

B v2.0.0

C

v1.0.0
v1.2.3
v2.0.0

D

v1.0.0
v1.2.3

💡 Hint

The pattern 'v1.*' matches tags starting with 'v1.' exactly.

The command lists all tags starting with 'v1.'. Tags 'v1.0.0', 'v1.10.0', and 'v1.2.3' match. 'v2.0.0' does not.

🧠 Conceptual

intermediate

Understanding semantic versioning tag meaning

In semantic versioning, what does the tag v2.3.0 indicate about the software compared to v2.2.5?

A A major update with breaking changes

B A pre-release version

C A patch update with only bug fixes

D A minor update with new features but backward compatible

💡 Hint

Semantic versioning format is MAJOR.MINOR.PATCH.

The minor version increased from 2 to 3, indicating new backward-compatible features. Patch updates fix bugs without new features.

🔀 Workflow

advanced

Create a new semantic version tag for a patch update

You have a repository with the latest tag v1.4.2. You fixed a bug and want to create a new patch version tag. Which command correctly creates the new tag v1.4.3 and pushes it to origin?

A git push origin v1.4.3 && git tag v1.4.3

B git tag v1.4.3 && git push origin v1.4.3

C git tag -a v1.4.3 -m 'Patch update' && git push origin v1.4.3

D git tag v1.4.3 -m 'Patch update' && git push origin v1.4.3

💡 Hint

Annotated tags include a message and are pushed explicitly.

Option C creates an annotated tag with a message and pushes it. Option C creates a lightweight tag without message. Option C has wrong flag usage. Option C pushes before tagging.

❓ Troubleshoot

advanced

Troubleshoot missing semantic version tags after clone

You cloned a repository but git tag shows no tags. What is the most likely reason?

A The repository has no tags at all

B Tags are not fetched by default during clone

C Tags are stored in a separate branch

D You need to run 'git init' after clone

💡 Hint

Tags are references that may not be fetched automatically.

By default, 'git clone' fetches tags, but if shallow clone or specific options are used, tags may be missing. Running 'git fetch --tags' fixes this.

✅ Best Practice

expert

Choose the best semantic version tag for a breaking change

You made a change that breaks backward compatibility in your software currently at v3.5.1. Which tag should you create next following semantic versioning?

A v4.0.0

B v3.6.0

C v3.5.2

D v3.5.1-beta

💡 Hint

Major version changes indicate breaking changes.

Semantic versioning requires incrementing the major version for breaking changes. Minor and patch versions are for backward-compatible changes.