Conversation
Previously the README said that bazelisk would discover the `.bazelversion` file "in the current directory or recursively any parent directory", but this wasn't the case. It would only find it in the root of the project. This doesn't work for cases where users have this layout for testing: ``` repo/MODULE.bazel repo/.bazelversion repo/e2e/MODULE.bazel ``` In this case it would only look beside `repo/e2e/MODULE.bazel`, not find the `repo/.bazelversion` and fallback to other logic. Folks often fix this by symlinking the root `.bazelversion` to the subdirectory. This changes the behavior to do what was stated before. The new behavior applies for the `.bazeliskrc` too. Fixes bazelbuild#52 Fixes bazelbuild#523
This was referenced Jul 15, 2026
Member
Author
|
I chose not to touch |
jkanywhere
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously the README said that bazelisk would discover the
.bazelversionfile "in the current directory or recursively any parentdirectory", but this wasn't the case. It would only find it in the root
of the project. This doesn't work for cases where users have this layout
for testing:
In this case it would only look beside
repo/e2e/MODULE.bazel, not findthe
repo/.bazelversionand fallback to other logic. Folks often fixthis by symlinking the root
.bazelversionto the subdirectory.This changes the behavior to do what was stated before. The new behavior
applies for the
.bazeliskrctoo.Fixes #52
Fixes #523