Introduce bazeliskVersion command#763
Merged
fweikert merged 1 commit intobazelbuild:masterfrom Jan 23, 2026
Merged
Conversation
…ersion and exits immediately. Fix bazelbuild#137 and bazelbuild#440.
Contributor
Author
|
@fweikert, what do you think about such an approach? |
fweikert
approved these changes
Jan 23, 2026
Member
|
Thank you! |
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
2 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.
Currently, bazelisk supports
versioncommand which is shared with Bazel itself. During the handling of this command, bazelisk prints its version and forwards the command line further to Bazel (downloading it if it's not already downloaded).As described in issues #137 and #440, there are scenarios when users are only interested in the bazelisk version, and don't want to download and run Bazel as a side effect.
For such scenarios, I suggest adding a separate command. It allows us to preserve the current behavior and to keep bazelisk being a transparent wrapper around Bazel, and at the same time provide a functionality for those who need it.
Fix #137 and #440.