1 / 5
Fill in: 'We ___ module versions so an upstream change can't silently break our stack.'
-
-
-
-
We 'pin versions' — the standard collocation for locking a dependency to a known-good release. The other options aren't idiomatic here.
2 / 5
Fill in: 'We ___ a module's changelog before bumping it in production.'
-
-
-
-
We 'review' a changelog — the standard, simple collocation. The other options are less idiomatic here.
3 / 5
Fill in: 'A breaking module change will ___ the plan with unexpected resource replacements.'
-
-
-
-
We say a change will 'litter' the plan — the standard collocation for cluttering it with unwanted diffs. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ a module upgrade in a sandbox account before touching production state.'
-
-
-
-
We 'test' an upgrade — the standard, simple collocation. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ semantic versioning so consumers know which bumps are safe.'
-
-
-
-
We 'follow' semantic versioning — the standard collocation for adhering to a convention. The other options are less idiomatic here.