bazelbuild / bazelbuild/rules_rust
cargo bazel repin changing the lock file
Open
needs-triage
- Dominant language
- Starlark
- Stars
- 843
- Forks
- 651
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 15
Description
using rules_rust 0.30.0 and rust 1.73.0
when i do `cargo build` or `cargo update` it results in an updated lock file like this:
however, running `CARGO_BAZEL_REPIN=1 bazelisk sync --only=crate_index` or `CARGO_BAZEL_REPIN=workspace bazelisk sync --only=crate_index` is somehow reverting this lock file change? why? and how can i prevent this behavior?
Contributor guide
Assessment
This issue has not been assessed yet.