Practise semantic versioning vocabulary: MAJOR.MINOR.PATCH, pre-release suffixes, version bumping, and communicating breaking changes clearly in English.
0 / 10 completed
1 / 10
A library is at version 1.4.2. The team fixes a small bug without changing the public API. Which version should they release next?
Bug fixes that do not break the API increment the PATCH segment. 1.4.2 → 1.4.3. The MAJOR and MINOR segments remain unchanged because no new features were added and no existing behaviour was broken.
2 / 10
A developer says: 'We're adding a new optional method to the public interface — no existing code breaks.' Which version bump is correct?
New, backwards-compatible functionality increments the MINOR version. Existing code keeps working. MAJOR is only for breaking (incompatible) changes.
3 / 10
What does the suffix '-rc.1' mean in version '3.0.0-rc.1'?
'rc' stands for release candidate. 3.0.0-rc.1 is a pre-release version intended for testing. If no blockers are found, it is promoted to the stable 3.0.0. Pre-release versions have lower precedence than the release (3.0.0-rc.1 < 3.0.0).
4 / 10
A team member says 'this is a breaking change.' In the context of SemVer, this means they must:
Under Semantic Versioning, any change that breaks the public API contract requires a MAJOR version increment. This signals to consumers that they cannot upgrade without reviewing migration notes.
5 / 10
In a pull request description a developer writes: 'bumping the version to 2.1.0 for this release.' What action is being described?
'Bumping the version' means updating the version field (in package.json, setup.py, pom.xml, etc.) to the next version number. It is a routine step before cutting a release, often automated with tools like npm version or semantic-release.
6 / 10
Sarah from QA just flagged a critical issue with the latest release of the 'WidgetLib'. The release notes state: 'Fixes a regression in user authentication.' In SemVer terms, what does 'regression' likely indicate about this update?
The term 'regression' in this context signifies that a previously functioning feature (user authentication) has unexpectedly stopped working correctly. This is a common usage when describing bug fixes; it's *not* about minor changes or performance. A breaking change would have used terms like 'removal' or 'deprecation'.
7 / 10
Mark is preparing a Slack message to announce a new release of the 'DataProcessor' library. He writes: 'We've released v2.3.1! This includes a minor update for improved error handling and performance.' What does 'minor update' suggest about the impact of this release on existing code?
'Minor update' in SemVer signals that only non-breaking changes have been introduced. This typically means no API modifications were made, and existing code should continue to function without requiring any alterations. Major or patch updates would use different terminology.
8 / 10
David is reviewing a pull request for the 'AuthService' library. The PR description reads: 'Bumping version to 4.0.0-beta.2 to accommodate upcoming API changes.' What does '-beta.2' signify within this version string?
The '-beta.2' suffix designates this as a beta (pre-release) version of the library. The 'beta' indicates that the changes are still under testing and might contain further modifications before becoming the stable 4.0.0 release. It signifies an unstable state.
9 / 10
Emily is discussing a proposed API update with her team. She says: 'We need to bump the version number when we introduce backwards incompatible changes.' What is Emily referring to in relation to Semantic Versioning?
Emily's statement highlights the core principle of Semantic Versioning: a major version bump (e.g., from 1.x to 2.x) is required whenever changes are made that break compatibility with older versions of the library. This signals to users that they *must* update their code.
10 / 10
John is writing a pull request description for a new release of the 'ImageConverter'. He writes: 'This update includes a breaking change: we've removed support for legacy image formats.' Which action does John describe in this PR?
'Breaking change' in this scenario indicates that the update introduces modifications that will cause existing code relying on the legacy image formats to fail. John is clearly informing users of a necessary upgrade and highlighting the potential disruption caused by the new release.
What will I practise in "Semantic Versioning Vocabulary"?
This module focuses on Package Management — 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 Package Management exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around package management — 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 Package Management exercises?
See the Package Management 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.