Switch to Bzlmod by default for managing external dependencies #213
Conversation
This file contains 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
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.
Switch from WORKSPACE-based to bzlmod-based dependency management by default.
WORKSPACE-based usage is still supported for users loading Stardoc's versioned distro tarballs,
but some packages (
//distro) in the git development tree will no longer load, and some ofStardoc's own golden tests will no longer pass, when using WORKSPACE.
Note that the new default behavior - when using Bzlmod for dependency management - is
that Stardoc uses
@stardocas its repo name. The legacy WORKSPACE-based setup uses@io_bazel_stardocas repo name. For compatibility with the legacyWORKSPACEsetup,and for ease of migration, users of Stardoc may load it via
bazel_dep(name = "stardoc", repo_name = "io_bazel_stardoc", ...)in theirMODULE.bazel.Fixes #189