bazelbuild / bazelbuild/rules_rust

cargo bazel repin changing the lock file

Open
#2,236 0 comments 0 reactions 0 assignees View on GitHub
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:
Screenshot 2023-11-02 at 6 21 29 PM

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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.