You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ever since switching from WORKSPACE to bazel modules, i no longer get repin warnings from rules_rust.
i do notice tho from time to time that the build from cargo build differs from bazel build and every time that happens i have to manually delete module.bazel.lock and run bazel build to recreate it.
i assume this is happening due to lack of repinning?
what is the recommended way to repin/keep bazel in sync with cargo.lock when using rules_rust with bazel modules.
The text was updated successfully, but these errors were encountered:
Does bazel mod deps --lockfile_mode=update work for you (see also here)? I just had the same issue and the docs of crate_universe do not seem up to date anymore as the advice on how to repin fail with ERROR: WORKSPACE has to be enabled for sync command to work, run with --enable_workspace. if you don't have a WORKSPACE anymore.
ever since switching from
WORKSPACE
to bazel modules, i no longer get repin warnings from rules_rust.i do notice tho from time to time that the build from
cargo build
differs frombazel build
and every time that happens i have to manually deletemodule.bazel.lock
and runbazel build
to recreate it.i assume this is happening due to lack of repinning?
what is the recommended way to repin/keep bazel in sync with
cargo.lock
when using rules_rust with bazel modules.The text was updated successfully, but these errors were encountered: