build: remove lockfile_mode

Author: longlho

.bazelrc

@@ -14,21 +14,6 @@ common --config=ruleset
 # Required until this is the default; expected in Bazel 7
 common --enable_bzlmod
 
-# Ensure that the MODULE.bazel.lock file is complete and committed.
-# This is an important security measure: it ensures that developers on the
-# same rule set download dependencies at the same versions with the same bits.
-# This setting does not affect modules that depend on this module.
-#
-# When updating dependencies, use --lockfile_mode=refresh, for example:
-#     bazel mod tidy --lockfile_mode=refresh
-#
-# When testing different versions of Bazel, use --lockfile_mode=update or
-# --lockfile_mode=off. The lock file format changes over time, and different
-# versions of Bazel may expect different syntax. Bazel also implicitly requires
-# some modules, and different versions have different dependencies, which
-# also affects the contents of the lock file.
-common --lockfile_mode=error
-
 # Load any settings specific to the current user.
 # .bazelrc.user should appear in .gitignore so that settings are not shared with team members
 # This needs to be last statement in this

.github/workflows/conventional-commits.yaml

@@ -5,6 +5,12 @@
 pre-commit:
   parallel: true
   commands:
+    bazel-lockfile:
+      glob:
+        - "*.bazel"
+        - "MODULE.bazel.lock"
+      run: bazel mod deps
+
     # Format code with oxfmt
     oxfmt:
       glob: "*.{js,ts,jsx,tsx,json,yaml,yml,md}"

lefthook.yml

@@ -107,11 +107,6 @@ common --incompatible_modify_execution_info_additive
 common --incompatible_strict_action_env
 # Docs: https://registry.build/flag/bazel?filter=incompatible_strict_action_env
 
-# Fail the build if the MODULE.bazel.lock file is out of date.
-# Using this mode in ci prevents the lockfile from being out of date.
-common:ci --lockfile_mode="error"
-# Docs: https://registry.build/flag/bazel?filter=lockfile_mode
-
 # On CI, don't download remote outputs to the local machine.
 # Most CI pipelines don't need to access the files and they can remain at rest on the remote cache.
 # Significant time can be spent on needless downloads, which is especially noticeable on fully-cached builds.