MODULE.bazel.lock file contains user specific paths #19621
Closed
Description
Description of the bug:
If you use a workspace local registry then the attributes recorded in the lockfile contain the expanded value for %workspace% instead of using the %workspace% placeholder.
Which category does this issue belong to?
External Dependency
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Use --registry=file://%workspace%/registry
and then depend on a module in that registry.
The applied patches from the registry are referenced using the expanded path of %workspace% instead of using a placeholder.
Which operating system are you running Bazel on?
Ubuntu linux
What is the output of bazel info release
?
6.4.0rc1
If bazel info release
returns development version
or (@non-git)
, tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD
?
No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response