Detect changes as a result of Bazel runs

[palfrey]

Description

Main item here was picking up changes to MODULE.bazel.lock. See example run at https://github.com/TraceMachina/nativelink/actions/runs/25171818162/job/73793030412?pr=2294

Type of change

Please delete options that aren't relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

CI

Checklist

• Updated documentation if needed
• Tests added/amended
• bazel test //... passes locally
• PR is contained in a single commit, using git amend see some docs

---

This change is 

[MarcusSorealheis]

The errant line is very strange, leading me to look further into the lock file itself.

[MarcusSorealheis]

Maybe try running this:

bazel clean
bazel build //... 2>&1
ls -la bc  # check timestamp and type

[jsharpe]

You can use https://bazel.build/reference/command-line-reference#common_options-flag--lockfile_mode specifically for MODULE.bazel.lock file changes - pass --lockfile_mode=error in CI.

[palfrey]

Maybe try running this:

bazel clean
bazel build //... 2>&1
ls -la bc  # check timestamp and type

This gets nothing locally. I've seen this before in Github actions runs, I think it's Github-specific.

[palfrey]

You can use https://bazel.build/reference/command-line-reference#common_options-flag--lockfile_mode specifically for MODULE.bazel.lock file changes - pass --lockfile_mode=error in CI.

Nice! Didn't know about that one. I've switched out the git diff work for adding this to all the Bazel calls in the workflows.