commit | 7018452ffac4fc070b29d5c5c872bac3c746a06a | [log] [tgz] |
---|---|---|
author | Yifan Hong <elsk@google.com> | Thu May 30 12:22:11 2024 -0700 |
committer | Yifan Hong <elsk@google.com> | Thu May 30 12:22:11 2024 -0700 |
tree | ba37a3bec581b913ab4e651ca177ba0205d21358 | |
parent | 8e4e793325543086752fd101f728beee4850888b [diff] | |
parent | 9f9108b2e8108d367ec21288ee269551ef759024 [diff] |
Upgrade bazel-central-registry to 9f9108b2e8108d367ec21288ee269551ef759024 This project was upgraded with external_updater. Usage: tools/external_updater/updater.sh update external/bazelbuild-bazel-central-registry For more info, check https://cs.android.com/android/platform/superproject/+/main:tools/external_updater/README.md Test: TreeHugger Change-Id: Ibcd5a8831bb11007621bb6922ba52ce8f31861d0
The default Bazel registry for the Bzlmod external dependency system of Bazel. It is the recommended place to find and publish your favorite Bazel projects. Visit https://registry.bazel.build to check what modules are already available!
To contribute, check our BCR policies and contribution guidelines.
The core infrastructure of the Bazel Central Registry depends on GitHub and Google Cloud. Bazel users who enable Bzlmod depend on the BCR by default. While we try to keep the BCR infrastructure simple and reliable, we assume no liability for any damages caused by build failures due to potential BCR infrastructure failures.
If you consider it necessary, you can do the following to avoid depending on the BCR infrastructure while still making use of the information checked into the BCR.
./bazel_registry.json
. You can run bazel run //tools:print_all_src_urls
to get the list of source URLs to mirror for all Bazel modules checked into the BCR. For example, https://foo.com/bar.zip
should be mirrored to https://<your mirror>/foo.com/bar.zip
.