I have observed some unexpected behavior after upgrading bazel-diff from version 12.0.0 to 25.0.0. It seems that after the upgrade, if a bazel macro defined in a ‘.bzl’ file is added or modified and then loaded even in an empty BUILD file, bazel-diff marks every bazel resource in the repository as impacted.
Here's the scenario I tested:
- I started with a repository containing a few bazel resources and ran bazel-diff to generate starting_hashes.json.
- Next, I added a simple bazel macro and loaded it in an empty BUILD file
- I then ran bazel-diff again to produce final_hashes.json, and used bazel-diff get-impacted-targets to identify impacted resources.
- Surprisingly, all bazel resources were listed as impacted.
I'm using Bazel version 9.1.0. I 've attached a minimal example, where I created a "test" directory containing the bazel macro to help illustrate the issue.
Could you help determine what might have changed in bazel-diff to cause this behavior? Any insights or suggestions would be greatly appreciated.
Thanks in advance for your help!
test-bazel-diff.zip
I have observed some unexpected behavior after upgrading bazel-diff from version 12.0.0 to 25.0.0. It seems that after the upgrade, if a bazel macro defined in a ‘.bzl’ file is added or modified and then loaded even in an empty BUILD file, bazel-diff marks every bazel resource in the repository as impacted.
Here's the scenario I tested:
I'm using Bazel version 9.1.0. I 've attached a minimal example, where I created a "test" directory containing the bazel macro to help illustrate the issue.
Could you help determine what might have changed in bazel-diff to cause this behavior? Any insights or suggestions would be greatly appreciated.
Thanks in advance for your help!
test-bazel-diff.zip