Practise the standard verbs for safely staging and testing dependency upgrades.
0 / 5 completed
1 / 5
Fill in: 'We ___ a dependency upgrade on a branch before merging to main, rather than a version bump nobody's actually tested in isolation.'
We 'stage an upgrade' — the standard, simple collocation for testing a dependency bump before merging. The other options are less idiomatic here.
2 / 5
Fill in: 'Bumping a major dependency without reading the changelog can ___ a build broken on a breaking change nobody's actually reviewed.'
We say an unreviewed bump will 'leave' the build broken — the standard, natural collocation for the resulting breakage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the changelog for breaking changes before upgrading, rather than a version nobody's actually read the release notes of.'
We 'review a changelog' — the standard, simple collocation for checking a dependency's release notes before upgrading. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every upgraded dependency against the full test suite, rather than a version nobody's actually confirmed still passes.'
We 'run a test suite' — the standard, simple collocation for validating a dependency upgrade against existing tests. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ outdated dependencies monthly across every service, rather than a version nobody's actually flagged as stale.'
We 'audit dependencies' — the standard, simple collocation for periodically checking for outdated packages. The other options aren't idiomatic here.