Fix Brotli, skcms, and x264 for FFmpeg (#10270) Fixes three dependency failures encountered while enabling FFmpeg's optional codecs in #10256, without changing published module versions: - `brotli@1.2.0.bcr.3` makes the 16-bit rotation and hash-counter conversions explicit so GCC 8 accepts the existing strict warnings. It removes the presubmit conversion-warning suppressions and adds an exhaustive rotation test. - `skcms@20250916.0.bcr.2` restores the per-element vector conversion for GCC before 9, where `__builtin_convertvector` is unavailable. Modern GCC and Clang keep the builtin. A public `skcms_Transform` test covers byte/float conversion, rounding, clamping, and partial SIMD batches; Debian 10 and Rocky Linux 8 join the existing platforms. - `x264@2023.10.1.bcr.3` downloads the same commit from the GitHub mirror after the VideoLAN URL returned inconsistent checksums in CI. The replacement archive matches the existing published SHA256 exactly. Its build targets and presubmit are unchanged. Local validation passes: GCC 8.5 builds all Brotli sources with strict warnings and passes the rotation test and CLI round trip; GCC 8.5 builds all skcms SIMD implementations and passes the transform test in fastbuild, opt, and dbg. Bazel 8.5 passes all 57 FFmpeg/dependency tests on macOS ARM64 with Clang 21, including FFmpeg's 52 tests with optional codecs enabled, the two new regression tests, and JPEG XL's three existing tests. Presubmit retains the existing build targets and configurations and now covers 78 configurations across the three modules. CI passes all 78 configurations, including the Bazel 7.x/8.x incompatible-flag reruns. Registry validation, formatting, tooling checks, and CLA checks also pass. [Buildkite results](https://buildkite.com/bazel/bcr-presubmit/builds/40204). The three modules retain their existing archive checksums. Brotli and skcms also retain their existing source URLs; x264 changes only the download host. These GitHub archives use BCR's documented URL-stability exception; archive integrity and source-repository checks remain enabled. -zbarskybot
The Bazel Central Registry (BCR) is the default registry for Bazel's external dependency system (“Bzlmod”). This is the GitHub repository backing the contents of the BCR, hosted at https://bcr.bazel.build/. For the website that allows you to search modules and see their versions conveniently, visit https://registry.bazel.build/.
Besides hosting metadata about Bazel-specific libraries (commonly known as “rulesets”), the BCR is also a central host for projects that don't have upstream support for Bazel (most commonly, C/C++ projects).
The BCR is just like a regular Bazel registry, with some extra metadata fields and policy restrictions. You can contribute to the BCR by sending pull requests; see BCR policies and contribution guidelines for more information.
The core infrastructure of the Bazel Central Registry depends on GitHub and Google Cloud. Bazel users who enable Bzlmod (the default since Bazel 8) 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.
--registry is a flag that can be specified multiple times.--registry flag is specified, the BCR is the only registry Bazel consults.--registry flag is specified, Bazel will consult the specified registries in order, but will not consult the BCR unless the BCR is explicitly specified as a registry. In other words, to use your own registry layered on top of the BCR, use --registry=https://my.own.registry.com/ --registry=https://bcr.bazel.build/../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.