I spent a while this weekend trying to figure out why a new project, which had a MODULE.bazel file (and a WORKSPACE.bzlmod), but no WORKSPACE file, was having the .bazelversion file ignored.
After some debugging I realized that bazelisk 1.18.0 only looks for .bazelversion in the repository root, and identifies the repository root by the presence of a WORKSPACE file.
Looks like this was fixed in b7f5c7570df35ce2273afa0c15f4bc5038fb126a, but we should cut a new Bazelisk release with that commit before Bazel 7.0 is released.
I spent a while this weekend trying to figure out why a new project, which had a
MODULE.bazel
file (and aWORKSPACE.bzlmod
), but noWORKSPACE
file, was having the.bazelversion
file ignored.After some debugging I realized that bazelisk 1.18.0 only looks for
.bazelversion
in the repository root, and identifies the repository root by the presence of aWORKSPACE
file.Looks like this was fixed in b7f5c7570df35ce2273afa0c15f4bc5038fb126a, but we should cut a new Bazelisk release with that commit before Bazel 7.0 is released.