The night before a library Wi-Fi automation change window, a city build pulls a new major of a shared HTTP client because dependencies floated on latest. Which practice would have kept the build reproducible?
Select an answer to reveal the explanation.
Short Explanation
Floating latest is like ordering 'whatever soup is popular today' the night of a banquet—surprises arrive. Exact pins or a lockfile freeze the recipe so the same build shows up for the change window.
Full Explanation
Dependency management in DEVCOR 1.11 emphasizes reproducible installs. Unpinned lower bounds can pull breaking majors; lockfiles or exact pins make the graph stable across machines and nights. Preferring prereleases or vendoring without versions does not solve reproducibility. The concept matters more than any single lockfile brand.