CI installs different transitive dependency versions than developers' laptops, and Elastic Beanstalk deploys then fail. What practice prevents that drift?
Select an answer to reveal the explanation.
Short Explanation
If CI and your laptop disagree on library versions, Beanstalk will referee—and citizens lose. Commit the lockfile and make CI install from it so the artifact matches what you tested. Floating ranges are how municipal builds go mysterious.
Full Explanation
Reproducible builds depend on lockfiles (npm, pip, Maven, and similar). Honoring them in CI ensures Elastic Beanstalk or other deploy artifacts match developer-validated dependency graphs. Floating transitive versions cause environment-specific failures that are hard to triage. Ad-hoc vendoring without a single lock-driven build worsens inconsistency.