Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start using bzlmod #165

Merged
merged 5 commits into from
Dec 17, 2023
Merged

Start using bzlmod #165

merged 5 commits into from
Dec 17, 2023

Conversation

martis42
Copy link
Owner

We can't use bzlmod with Bazel versions < 6.2.0.

Publishing DWYU to the central registry will be done in later steps. For now we only enable using bzlmod while developing.
One downside of bzlmod is that rules_python no longer allows defining the Python toolchain with patch level precision. As a consequence we have to change the Python toolchains to the defaults defined by rules_python.

We can't use bzlmod with Bazel versions < 6.2.0.
Publishing DWYU to the central registry will be done in later steps. For now
we only enable using bzlmod while developing.
One downside of bzlmod is that rules_python no longer allows defining the
Python toolchain with patch level precision. As a consequence we have to
change the Python toolchains to the defaults defined by rules_python.
Now that the external integration testing repos are mentioned in a root
level file their names should be more descriptive.
@martis42 martis42 merged commit 5f0b209 into main Dec 17, 2023
4 checks passed
@martis42 martis42 deleted the start_using_bzlmod branch December 17, 2023 13:18
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.

None yet

1 participant