Add 1.3.1.bcr.5 with @platforms//os:macos copts (#3705) Protobuf's [zlib.BUILD](https://github.com/protocolbuffers/protobuf/blob/main/third_party/zlib.BUILD#L62) that the current add_build_file.patch is based off of has an extra select condition for macOS to exclude "-Wno-deprecated-non-prototype". This is missing from BCR which otherwise fails with `error: unknown warning option '-Wno-deprecated-non-prototype' [-Werror,-Wunknown-warning-option]` e.g. [error when we migrate macOS tests to bzlmod]( https://github.com/protocolbuffers/protobuf/actions/runs/13079734633/job/36500354192?pr=20090) Adding a new 1.3.1.bcr.5 patch to add the corresponding condition for @platforms//os:macos, but let me know if this type of minor patch should actually be made directly in an existing 1.3.1 or 1.3.1.bcr.N version instead.
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.