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.

Practice

1. What does the PATCH number represent in semantic versioning like 1.4.2?

easy

A. Build metadata or pre-release information

B. New features added in a backward-compatible way

C. Major changes that break backward compatibility

D. Bug fixes and small changes that do not affect the API

Solution

1. Step 1: Understand semantic versioning parts

   Semantic versioning uses MAJOR.MINOR.PATCH format where PATCH is the last number.

2. Step 2: Identify PATCH meaning

   PATCH is for bug fixes or small improvements that do not change the API or features.

3. Final Answer:

   Bug fixes and small changes that do not affect the API -> Option D

4. Quick Check:

   PATCH = bug fixes [OK]

Hint: PATCH fixes bugs without changing features [OK]

Common Mistakes:

• Confusing PATCH with MINOR or MAJOR
• Thinking PATCH adds new features
• Mixing PATCH with build metadata

2. Which git command correctly creates an annotated tag named v2.1.0 with a message?

easy

A. git tag -a v2.1.0 -m "Release version 2.1.0"

B. git tag v2.1.0 -m "Release version 2.1.0"

C. git tag -m "Release version 2.1.0" v2.1.0

D. git tag --message v2.1.0 "Release version 2.1.0"

Solution

1. Step 1: Recall annotated tag syntax

   Annotated tags use -a and -m for message: git tag -a tagname -m "message".

2. Step 2: Match correct command

   git tag -a v2.1.0 -m "Release version 2.1.0" matches this syntax exactly, others misuse flags or order.

3. Final Answer:

   git tag -a v2.1.0 -m "Release version 2.1.0" -> Option A

4. Quick Check:

   Annotated tag = git tag -a -m [OK]

Hint: Use -a and -m together for annotated tags [OK]

Common Mistakes:

• Omitting -a for annotated tags
• Placing -m before tag name incorrectly
• Using --message instead of -m

3. Given these git tags: v1.0.0, v1.2.0, v1.2.3, what will git describe --tags output if the current commit is exactly at v1.2.3?

medium

A. v1.2.3

B. v1.2.3-0-g

C. v1.2.0

D. v1.2.3-1-g

Solution

1. Step 1: Understand git describe output

   If the current commit matches a tag exactly, git describe --tags outputs just that tag name.

2. Step 2: Apply to given tags

   Since current commit is exactly at v1.2.3, output is v1.2.3 without extra suffix.

3. Final Answer:

   v1.2.3 -> Option A

4. Quick Check:

   Exact tag commit = tag name only [OK]

Hint: Exact tag commit shows tag name only [OK]

Common Mistakes:

• Expecting extra suffix even on exact tag
• Confusing closest previous tag with current
• Misunderstanding commit hash suffix

4. You tried to create an annotated tag with git tag -m "Release 1.0" v1.0.0 but it created a lightweight tag instead. What is the error?

medium

A. Using double quotes instead of single quotes for message

B. Incorrect order of arguments; message must come after tag name

C. Missing -a flag to create an annotated tag

D. Tag name v1.0.0 is invalid

Solution

1. Step 1: Check command syntax for annotated tags

   Annotated tags require -a flag; -m alone creates lightweight tag with message ignored.

2. Step 2: Identify missing flag

   The command lacks -a, so it made a lightweight tag instead of annotated.

3. Final Answer:

   Missing -a flag to create an annotated tag -> Option C

4. Quick Check:

   Annotated tag needs -a flag [OK]

Hint: Always use -a for annotated tags [OK]

Common Mistakes:

• Omitting -a flag
• Thinking -m alone creates annotated tag
• Confusing argument order

5. You want to tag a release as v3.0.0 but only if the current commit is ahead of v2.9.9 by at least one commit. Which sequence of commands correctly checks this and creates an annotated tag if true?

hard

A. git describe --tags --match "v2.9.9" && git tag -a v3.0.0 -m "Release v3.0.0"

B. if [ $(git rev-list v2.9.9..HEAD --count) -gt 0 ]; then git tag -a v3.0.0 -m "Release v3.0.0"; fi

C. git tag -a v3.0.0 -m "Release v3.0.0" && git rev-list v2.9.9..HEAD --count

D. git tag v3.0.0 && git rev-list --count v2.9.9..HEAD

Solution

1. Step 1: Check commits ahead of v2.9.9

   Use git rev-list v2.9.9..HEAD --count to count commits ahead.

2. Step 2: Conditional tag creation

   If count is greater than 0, create annotated tag with git tag -a v3.0.0 -m "Release v3.0.0".

3. Final Answer:

   if [ $(git rev-list v2.9.9..HEAD --count) -gt 0 ]; then git tag -a v3.0.0 -m "Release v3.0.0"; fi -> Option B

4. Quick Check:

   Count commits then tag if ahead [OK]

Hint: Count commits ahead before tagging [OK]

Common Mistakes:

• Tagging without checking commit count
• Using git describe incorrectly for this check
• Creating lightweight tag instead of annotated