Dependency Management: Phrases for Library Upgrades & Breaking Changes
5 exercises on dependency management vocabulary. Choose the most natural and professional option.
0 / 10 completed
1 / 10
You've discovered that a core library your team uses is no longer receiving security patches. How do you raise this?
"This library has reached end-of-life" is the precise technical and vendor-standard phrasing for software that no longer receives updates or security patches. "Before the next security advisory hits us" gives urgency without alarmism. Real examples: "Node 16 has reached end-of-life — we need to migrate to 20 LTS this quarter"; "OpenSSL 1.1 is EOL — any dependency on it is now a security liability." Options B-D describe the problem informally without using the accepted term, which weakens the case for prioritisation.
2 / 10
Your team wants to lock the dependency to prevent unexpected breaking upgrades from Dependabot. What do you recommend?
"We should pin the version to X.Y.Z" is the correct dependency management phrasing. Pinning to an exact version (not a range) prevents automatic upgrades. The "until we've validated the upgrade path" clause shows this is a temporary, deliberate choice — not negligence. Real examples: "Pin lodash to 4.17.21 — the 5.x upgrade has breaking changes we haven't assessed"; "We're pinning the ORM to 3.x until the migration guide for v4 is published." Options A/B/D avoid the technical term "pin" and are less precise.
3 / 10
You need to explain how your team will migrate from an old library version to a new one. What do you say?
"The upgrade path is: step 1, step 2, step 3" is the expected format for communicating a library migration plan. It shows you've thought through sequencing, risk mitigation (parallel run), and cleanup. Real examples: "Upgrade path: shim the old API for 2 weeks, migrate call sites, remove shim"; "Upgrade path is documented in the wiki — we'll use a compatibility layer through Q3." Options A-C are vague about the actual plan and don't name the mechanism.
4 / 10
A new major version of a key library introduces incompatibilities with your current code. How do you inform the team?
"There's a breaking change in v3 — X changed. Migration guide is at Y" is the complete breaking-change communication: it names the version, the specific change, and where to find help. Real examples: "Breaking change in v2: all async handlers now return Promises — check the upgrade guide"; "Breaking change in Axios 1.0: the error structure changed — migration steps in the release notes." Options A/C/D don't name the specific breaking change or point to a migration resource.
5 / 10
Before agreeing to add a new library to the project, what do you propose checking first?
"I'd audit the transitive dependencies first" is the expert's framing — it goes beyond the library itself to the full dependency tree. Mentioning licensing and security risks shows security-aware thinking. Real examples: "Audit the transitive deps before adding — that 'tiny' library pulled in 50 packages last time"; "Transitive dependency audit: this SDK brings in aws-sdk v2, which we're trying to eliminate." Options B-D are valid concerns but too surface-level; none address the hidden risk of transitive dependencies specifically.
6 / 10
Code Review Comment: 'I'm seeing a warning about an outdated version of the lodash library in this component. The team lead suggested we just ignore it for now. What's your response?',
Ignoring warnings is rarely a good practice in software development. The core point here is that outdated libraries can introduce security vulnerabilities or unexpected behavior. The correct response acknowledges the warning and proposes further investigation – a proactive approach is key when dealing with dependency issues. Option A is too dismissive; option D doesn't address the problem.
7 / 10
Slack Message: '@john.doe Just noticed that upgrading to version 2.1 of react-hooks broke our data fetching in the `UserProfile` component. The build is failing.' What's the best follow-up message to send?',
A clear and actionable response is crucial when a dependency upgrade causes problems. Simply acknowledging the issue isn't enough; you need detailed information to understand the root cause. The error logs and a minimal reproducible example allow the team to quickly diagnose and fix the issue – this demonstrates effective debugging practices. Option A lacks substance, while options B and C are premature reactions.
8 / 10
PR Description: 'Updating to express v4.18.2. This change includes security patches and performance improvements. Please review carefully for any breaking changes.' Which of the following is MOST important to include in this PR description?
While a general description is helpful, the most critical information when upgrading a library is to highlight potential breaking changes. Developers need to be aware of these changes to proactively address them and avoid introducing regressions. The PR description should clearly communicate the scope of the change and what needs to be tested. Option A focuses on perceived benefits, while options B and C are less relevant in this context.
9 / 10
Standup Update: 'Today I'm working on migrating our backend service to use the new axios library. We're aiming for a seamless transition with minimal downtime.' What question should you ask the team to ensure success?
A successful dependency migration requires careful planning and rigorous testing. Simply replacing instances of the old library is risky and doesn't account for potential incompatibilities. Testing in a staging environment allows you to identify and resolve issues before deploying to production. Option A is too simplistic; option D is important but secondary to ensuring functionality.
10 / 10
API Response (from Dependency Manager): The dependency manager's output shows a proposed upgrade to moment.js v7.0.0. It indicates potential breaking changes due to the library's deprecation. What is the FIRST thing you should do?
Before taking any action, you must understand the implications of the proposed upgrade. The release notes for `moment.js` v7.0.0 will detail the breaking changes and provide guidance on how to address them. Ignoring the warning is a dangerous practice that could lead to significant problems down the line. Option A is premature; options C and D are reactive rather than proactive.
What will I practise in "Dependency Management: Phrases for Library Upgrades & Breaking Changes"?
This module focuses on Phrasebook — 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 Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — 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 Phrasebook exercises?
See the Phrasebook 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.