Description of the problem / feature request:
Although the algorithm used by bzlmod should lead to stable results, having to recalculate the dependency tree with each build is wasteful and may prevent reproducible builds, particularly of historic commits. The WORKSPACE file locked everything down, so there was no need to worry about this, but it would be useful if bzlmod had a lock file it could (optionally) use.
Feature requests: what underlying problem are you trying to solve with this feature?
I want reproducible builds, even if someone has yanked a module since the last build.
What's the output of bazel info release?
release 5.0.0rc3
Description of the problem / feature request:
Although the algorithm used by
bzlmodshould lead to stable results, having to recalculate the dependency tree with each build is wasteful and may prevent reproducible builds, particularly of historic commits. TheWORKSPACEfile locked everything down, so there was no need to worry about this, but it would be useful ifbzlmodhad a lock file it could (optionally) use.Feature requests: what underlying problem are you trying to solve with this feature?
I want reproducible builds, even if someone has yanked a module since the last build.
What's the output of
bazel info release?release 5.0.0rc3