Gradle build fails when dependency resolution would update lockfile
Goal Our team wants a repeatable development environment using Gradle dependency locking so resolved dependency versions stay consistent across local machines and CI. Gradle writes lockfiles recording resolved versions, repositories, and metadata. During a normal build, Gradle does not automatically regenerate these lockfiles; if resolution would change a re
gradle