Fails to detect my current Bazel version

[luispadron]

Using flags from Bazel 9.0.0-pre.20250121.1 because auto-detecting the Bazel version failed

Any way to get more info about what's failing here? Love this tool btw!

[vogelsgesang]

ok, I need to add more logging - the curse of people actually using the software... 🙂

Couple of points that come to my mind:

• Do you have a WORKSPACE, WORKSPACE.bazel, MODULE.bazel or REPO.bazel?
• If so, do you have a .bazeliskrc or .bazelversion file in the same folder as that file?
• Could you share the contents of your .bazeliskrc / .bazelversion file?

[luispadron]

• Do you have a WORKSPACE, WORKSPACE.bazel, MODULE.bazel or REPO.bazel?

We have just a MODULE.bazel using Bazel 7.5.0

• If so, do you have a .bazeliskrc or .bazelversion file in the same folder as that file?

We have both, here is the contents:

# .bazelversion
7.5.0

# .bazeliskrc
BAZELISK_WRAPPER_DIRECTORY=./Tools

[vogelsgesang]

We have both

Ah, so that's probably where the issue is. Could you temporarily delete the .bazeliskrc and check if the issue goes away? I.e. in VS-Code run the "Developer: Reload Window" command and open the bazelrc files. The issue should have disappeared with the .bazeliskrc gone.

The issue is this code snippet. As you can see, if we find a .bazeliskrc, we don't check for a .bazelversion anymore.

Let me know if want to get your hands dirty in Rust and prepare a pull request by yourself 🙂
The actual code change would only be a couple of lines. No test cases for that particular part, unfortunately, since I didn't figure out how to mock out file-system APIs in Rust, yet...

Besides the code change, this would also involve a bit of research into the logic used by bazelisk. E.g., what should happen if there are versions defined in both the .bazeliskrc and the .bazelversion? Which one should take precedence?

[luispadron]

Yep deleting the .bazeliskrc allows it to find the right version! I'll try to PR something in a few