-
Notifications
You must be signed in to change notification settings - Fork 15.5k
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
Migrate to Bzlmod for managing external dependencies #14313
Comments
This will help make sure [Bazel Downstream Pipeline](https://github.com/bazelbuild/continuous-integration/blob/master/docs/downstream-testing.md) is green after enabling Bzlmod at Bazel@HEAD See bazelbuild/bazel#18958 (comment) Related #14313 Closes: #14314 PiperOrigin-RevId: 572848360
This will help make sure [Bazel Downstream Pipeline](https://github.com/bazelbuild/continuous-integration/blob/master/docs/downstream-testing.md) is green after enabling Bzlmod at Bazel@HEAD See bazelbuild/bazel#18958 (comment) Related #14313 Closes: #14314 PiperOrigin-RevId: 572848360
This will help make sure [Bazel Downstream Pipeline](https://github.com/bazelbuild/continuous-integration/blob/master/docs/downstream-testing.md) is green after enabling Bzlmod at Bazel@HEAD See bazelbuild/bazel#18958 (comment) Related #14313 Closes: #14314 PiperOrigin-RevId: 572920528
This requires: * Tentatively abandoning the use of Bzlmod. Protobuf doesn't support bzlmod yet [1] and the latest available protobuf in the Bazel Central Registry is 21.7 which provides incompatible JSON APIs [2]. Moving forward, we can re-introduce bzlmod when protobuf and Abseil officially support it. * Using the `--output_base=C:\O ` Bazel statup option on Windows [3] when building for Kokoro tests. [1] protocolbuffers/protobuf#14313 [2] https://github.com/bazelbuild/bazel-central-registry/tree/7004deef786dc4152eedd3dfedf91b5b6b4590d4/modules/protobuf [3] protocolbuffers/protobuf#12947 PiperOrigin-RevId: 586313367 Change-Id: Idc3f6d5a6e34b7da8fe51ea42ca354027a94a369
This requires: * Tentatively abandoning the use of Bzlmod. Protobuf doesn't support bzlmod yet [1] and the latest available protobuf in the Bazel Central Registry is 21.7 which provides incompatible JSON APIs [2]. Moving forward, we can re-introduce bzlmod when protobuf and Abseil officially support it. * Using the `--output_base=C:\O ` Bazel statup option on Windows [3] when building for Kokoro tests. [1] protocolbuffers/protobuf#14313 [2] https://github.com/bazelbuild/bazel-central-registry/tree/7004deef786dc4152eedd3dfedf91b5b6b4590d4/modules/protobuf [3] protocolbuffers/protobuf#12947 PiperOrigin-RevId: 586313367
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment. This issue is labeled |
ping, to keep it active |
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment. This issue is labeled |
. |
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment. This issue is labeled |
. |
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment. This issue is labeled |
This is still active and will help downstream migration to BZLMOD |
Should be able to close this with the addition of MODULE.bazel since ~v27.x. See https://github.com/bazelbuild/bazel-central-registry/tree/main/modules/protobuf. Please reopen (or file a new issue) for any dependencies missing in bzlmod. |
With future Bazel LTS versions, Bzlmod will become the default system for external dependencies management.
Please consider migrating all your external dependencies in WORKSPACE to MODULE.bazel
For more information, please check bazelbuild/bazel#18958
Related issue is #13618, but #13618 is more about providing a Bazel modules for users, this one is for tracking the migration of protobuf itself to use Bzlmod for managing both prod and dev external deps.
The text was updated successfully, but these errors were encountered: