Skip to content

fix: add development version to list supporting bzlmod#408

Merged
withered-magic merged 1 commit intowithered-magic:mainfrom
patrickdoc:patrickdoc/dev-version
Sep 23, 2025
Merged

fix: add development version to list supporting bzlmod#408
withered-magic merged 1 commit intowithered-magic:mainfrom
patrickdoc:patrickdoc/dev-version

Conversation

@patrickdoc
Copy link
Contributor

If you use a development version of Bazel, the current logic doesn't identify it as supporting bzlmod. You can reproduce by pointing bazelisk at a sha instead of a release version:

diff --git a/.bazeliskrc b/.bazeliskrc
index 330b936..1df2767 100644
--- a/.bazeliskrc
+++ b/.bazeliskrc
@@ -1 +1 @@
-USE_BAZEL_VERSION=8.2.1
+USE_BAZEL_VERSION=2f67489da598c37d45c9b2b8601740d6e5a34851

And then checking the info:

$ bazelisk info
...
release: development version

This PR assumes that any development versions support bzlmod since it has been default for a while now, so it seems ~mostly safe.

@withered-magic
Copy link
Owner

Thank you!

@withered-magic withered-magic merged commit 5bb6ae4 into withered-magic:main Sep 23, 2025
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants