migrate to bzlmod module #9
Conversation
|
This is good, but I would like to maintain support for legacy workspace mode as well (we're still using workspace at work). In this PR you've kept the workspace example around, but it doesn't work. I'm not familiar with the best way to approach supporting both bzlmod and workspace, so I'm not sure what it should look like yet. I can do this migration myself when I have time, but I don't have time at the moment. |
|
@Calsign as far as I understand, you want to maintain that the repo can be still consumed via workspace, correct? Because even with only bzlmod used in this repo, the project should be still able to be pull in in workspace files using http archive. Given that with bazel 7 bzlmod is the default, and with bazel 8, workspace is disabled by default it might make sense to move forward with this repo as bazel only. Of course, we want to make sure that it can still be consumed correctly which could be done by an example. |
| @@ -17,4 +17,4 @@ build --config=clippy | |||
|
|
|||
| build:ci --keep_going --experimental_scale_timeouts=3 --config=check | |||
|
|
|||
| common --noenable_bzlmod | |||
| common --enable_bzlmod | |||
There was a problem hiding this comment.
This can be removed as it is enabled by default
Migrate the workspace to blzmod to release on Bazel Central Registry