| commit | c775fba20f068df91369d3c311a5097911f17cea | [log] [tgz] |
|---|---|---|
| author | publish-to-bcr-bot[bot] <112732530+publish-to-bcr-bot[bot]@users.noreply.github.com> | Wed May 15 11:59:18 2024 +0200 |
| committer | GitHub <noreply@github.com> | Wed May 15 11:59:18 2024 +0200 |
| tree | 7335c905290bd76861c1312cb670ecdd49fbcfbd | |
| parent | ae674bb42d0856c27ee86b27f6170c00c8b1476a [diff] |
bazel_features@1.11.0 (#2038) Release: https://github.com/bazel-contrib/bazel_features/releases/tag/v1.11.0 _Automated by [Publish to BCR](https://github.com/apps/publish-to-bcr)_ Co-authored-by: Xùdōng Yáng <wyverald@gmail.com>
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.