Clarify Bazel lockfile verification failures (#46993)

A failed lockfile check does not necessarily mean `MODULE.bazel.lock` is
out of date. Update the shell script and Windows recipe to direct users to
the Bazel error and recommend `just bazel-lock-update` only when Bazel
reports an out-of-date lockfile.

GitOrigin-RevId: cf156a83b931f5109d1382190b475e496e1bfad0
This commit is contained in:
jif
2026-09-21 10:01:13 +00:00
committed by copyberry
parent 48f897e4ce
commit f747d23d4b
2 changed files with 3 additions and 3 deletions
+2 -2
View File
@@ -3,7 +3,7 @@ set -euo pipefail
repo_root="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
if ! "${repo_root}/.github/scripts/run_bazel_with_buildbuddy.py" mod deps --lockfile_mode=error; then
echo "MODULE.bazel.lock is out of date."
echo "Run 'just bazel-lock-update' and commit the updated lockfile."
echo "Unable to verify MODULE.bazel.lock; see the Bazel error above."
echo "If Bazel reports an out-of-date lockfile, run 'just bazel-lock-update' and commit the updated lockfile."
exit 1
fi