5 exercises — every developer reads and writes changelogs, migration guides, and release announcements. Identifying the correct version type shows you understand semantic versioning and breaking change principles.
Semantic versioning: MAJOR.MINOR.PATCH
MAJOR (5.0.0) — breaking change; existing code may stop working; requires migration
MINOR (3.2.0) — new backwards-compatible feature; existing code keeps working
Hotfix — emergency patch pushed outside the normal release cycle for a critical/security issue
0 / 10 completed
1 / 10
A changelog entry reads:
"v2.4.1 — Fixed a typo in the validation error message shown when an email address is too long."
What kind of version bump is this?
Patch version — the third number in semantic versioning (MAJOR.MINOR.PATCH). Patch releases fix bugs, typos, and other small issues. No new features are added. No existing behaviour breaks. Semver rule: increment PATCH when you make backwards-compatible bug fixes.
The three semver numbers in plain English: • MAJOR (2.x.x): Breaking change — existing code may stop working • MINOR (x.4.x): New feature — backwards compatible; nothing breaks • PATCH (x.x.1): Bug fix — backwards compatible; nothing new
A typo fix in a UI message does not add any new capability and does not break anything → it is a patch. "Hotfix" specifically means an emergency patch pushed directly to production outside the normal release cycle — it is a process distinction, not a version number category.
2 / 10
A library changelog states:
"v3.2.0 — Added a new optional retryConfig parameter to the createClient() function. Existing calls without this parameter continue to work as before."
What kind of version bump is this?
Minor version — a new feature or capability that is backwards compatible (existing integrations keep working without changes). Adding an optional parameter does not break any existing call sites. Semver rule: increment MINOR when you add functionality in a backwards-compatible manner.
Non-breaking vs. breaking changes — key distinction: • Adding an optional parameter → minor (non-breaking) • Adding a required parameter → major (breaking — all callers must update) • Changing a parameter type → major (breaking) • Removing a function → major (breaking) • Fixing a bug in an existing function → patch
The changelog phrase "existing calls without this parameter continue to work" is a signal that this is a non-breaking addition → minor.
3 / 10
A migration guide reads:
"v5.0.0 — The deprecated /api/v1/users endpoint has been removed. This endpoint was deprecated in v4.0 with a 12-month migration window. Please use /api/v2/users instead."
What kind of version bump is this?
Major version — any change that breaks backward compatibility requires a major version bump. Removing a public API endpoint, even one that was deprecated, means all clients still using /api/v1/users will get a 404 after upgrading. That is a breaking change → major. Semver rule: increment MAJOR when you make incompatible API changes.
Common breaking changes that require a major version: • Removing a public API endpoint, function, or method • Changing a function's return type or parameter types • Renaming a required configuration key • Changing the authentication mechanism • Removing or renaming a database column in a shared schema
The deprecation process in practice: deprecate in MINOR version (add @deprecated warning) → maintain for a set period → remove in next MAJOR version. The phrase "deprecated in v4.0 with a 12-month migration window" confirms this followed the standard process.
4 / 10
An engineering notice reads:
"URGENT — v2.8.4 released. This is an emergency release addressing CVE-2026-4412, a critical authentication bypass vulnerability in the session validation layer. All teams must upgrade immediately."
What kind of version bump is this?
Hotfix — an emergency release that goes directly to production, bypassing the normal development-staging-release cycle. Hotfixes are patches (they don't add features), but the term "hotfix" specifically refers to the urgency and process, not just the version bump category. Version number: patch-style increment (2.8.3 → 2.8.4).
When "hotfix" is used vs. "patch": • Patch: scheduled bug fix in the normal release cycle • Hotfix: emergency out-of-band fix, usually for P1/critical issues
Triggers for a hotfix: critical security vulnerability (CVE), data corruption bug, total service outage or regression, payment processing failure.
Hotfix workflow: branch from the current production tag (not from develop) → apply minimal fix → test → deploy → backport to develop/main. The signal words in this question are "URGENT", "emergency release", "CVE", and "must upgrade immediately".
5 / 10
A PR description reads:
"Internally rewrote the database connection pooling module from a custom implementation to HikariCP. All public API methods retain identical signatures — no interface changes. Performance improved by 40% under high load."
What kind of version bump is likely appropriate for this release?
Patch version — if the public API is identical (same method signatures, same behavior contract, same configuration keys) and no new user-visible features are added, an internal implementation swap is a patch-level change. In semver, what matters is the observable interface contract, not the internal implementation details. Semver rule: if no API changes and no new capabilities → patch.
Key phrase in the PR:"All public API methods retain identical signatures" — this is the decisive signal. From the consumer's perspective, nothing changes; the upgrade is transparent.
When an internal rewrite might require a minor or major bump: • If the new implementation adds new configuration options → minor • If the new implementation changes error types thrown → major (breaks error handling code) • If the new implementation removes a configuration key that existed before → major
In practice: teams sometimes bump minor for significant internal rewrites even if not strictly required by semver — to signal to users that thorough re-testing is advised.
6 / 10
Sarah from the Security team sent this Slack message: 'Hey team, we just pushed v1.0.3 – a hotfix for a potential XSS vulnerability discovered in the admin panel. Please review and test thoroughly.' Considering Sarah's message, what type of version bump does v1.0.3 represent?
Hotfixes are always classified as patch releases because they address immediate issues like vulnerabilities. A minor bump indicates that the change is backwards compatible and doesn't affect existing functionality. Major bumps usually involve new features or breaking changes, which isn't implied here. Therefore, a patch release (version 3) is the correct classification.
7 / 10
You're reviewing a Pull Request for a new feature in the payment processing library. The PR description reads: 'Implemented support for Apple Pay using the Stripe API. This adds a new paymentMethodType property to the PaymentRequest object and includes handling for Apple Pay transactions.' What kind of version bump is most appropriate for this release?
Adding a new, supported payment method (like Apple Pay) is generally considered a minor release because it doesn't fundamentally change how existing functionality works. The addition of a new property and API handling remains compatible with older versions. A major bump would imply a complete overhaul, while patches address bugs and releases are pre-production steps.
8 / 10
The release notes for the logging service state: 'v4.2.0 – Refactored the internal error reporting mechanism to use a distributed tracing system (Jaeger). This improves observability and reduces latency.' What kind of version bump is this?
Refactoring the internal error reporting system to use Jaeger (a distributed tracing system) is an improvement that's generally considered backwards compatible. This means existing consumers of the logging service should continue to work without modification – therefore it's classified as a minor release. A major bump would signify significant architectural changes.
9 / 10
During a standup meeting, Ben from the Infrastructure team announced: 'We've deployed v7.1.2 – a critical update to address a memory leak discovered in the caching service. This release includes immediate remediation.' What kind of version bump is this?
The term 'critical update' and the description of remediating a memory leak strongly indicate a patch release. Patch releases are used to fix bugs or address vulnerabilities that may cause system instability. While performance optimization could be part of a minor release, it's not the primary driver here – the immediate focus is on fixing a critical issue.
10 / 10
You are reviewing the changelog for the API gateway: 'v8.0.0 – Introduced support for OAuth 2.0 authentication and authorization flows. Existing API keys remain functional.' What kind of version bump does this represent?
Introducing OAuth 2.0 support is a significant change to the API gateway's security model and adds a non-breaking feature. While existing API keys continue to work, the addition of a new authentication method constitutes a minor bump. A major release would indicate a complete overhaul or breaking changes.
What will I practise in "Read Release Notes: Which Version Bump?"?
This module focuses on Numbers, Data & Metrics — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Numbers, Data & Metrics exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around numbers, data & metrics — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Numbers, Data & Metrics exercises?
See the Numbers, Data & Metrics hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.