In cargo raze 0.12.0, when generating Bazel rules for a workspace of multiple packages, the BUILD.bazel file for each package has alias rules for just the dependencies of that package.
In cargo raze 0.13.0, this behavior changed to add aliases for all the dependencies of every package in the workspace.
This causes Bazel alias conflicts when two packages within the workspace depend on different major versions of a crate (e.g., clap 2.x vs 3.x). In such cases, the Bazel project can no longer build.
It is possible that issue #474 might be reflecting this deeper problem.
In cargo raze 0.12.0, when generating Bazel rules for a workspace of multiple packages, the
BUILD.bazelfile for each package hasaliasrules for just the dependencies of that package.In cargo raze 0.13.0, this behavior changed to add aliases for all the dependencies of every package in the workspace.
This causes Bazel alias conflicts when two packages within the workspace depend on different major versions of a crate (e.g., clap 2.x vs 3.x). In such cases, the Bazel project can no longer build.
It is possible that issue #474 might be reflecting this deeper problem.