Google Git
Sign in
android / platform / external / bazelbuild-bazel-central-registry / refs/heads/main
commit69aaa07f2c2f3241b98af6b18612d47a0c19995e[log] [tgz]
authorHONG Yifan <elsk@google.com>Fri Dec 06 14:42:24 2024 -0800
committerHONG Yifan <elsk@google.com>Fri Dec 06 14:42:24 2024 -0800
tree178e331a1f3e0758b81d064f300efe73aa78bdbf
parent320e66e5967a6a19bc8dcc7bdad4052e9a74e40e [diff]
parent36eb180c1afa8f3265758d69d2f4b2979fbd208d [diff]
Upgrade bazel-central-registry to 36eb180c1afa8f3265758d69d2f4b2979fbd208d

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/+/main:tools/external_updater/README.md

Bug: 372860136
Test: TreeHugger
Change-Id: Iec3c00f762ce775556baa54970b04c4bec01b1c3
tree: 178e331a1f3e0758b81d064f300efe73aa78bdbf
  1. .bazelci/
  2. .github/
  3. docs/
  4. modules/
  5. tools/
  6. .bazelignore
  7. .bazelversion
  8. .editorconfig
  9. .git-blame-ignore-revs
  10. .gitattributes
  11. .gitignore
  12. .pre-commit-config.yaml
  13. .ruff.toml
  14. AUTHORS
  15. bazel_registry.json
  16. BUILD
  17. LICENSE
  18. METADATA
  19. metadata.schema.json
  20. MODULE.bazel
  21. MODULE_LICENSE_APACHE2
  22. OWNERS
  23. README.md
  24. WORKSPACE
README.md

Bazel Central Registry

Overview

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!

Contributing

To contribute, check our BCR policies and contribution guidelines.

Depending on the BCR infrastructure (and how not to)

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.

  • Clone the BCR repository or mirror the content to your own infrastructure and use the --registry option to change the default Bazel registry to your own.
  • Host your own mirror for all source archive URLs and add the mirror URL in ./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.