feat: add `hiredis@1.3.0` (#5877) > Hiredis is a minimalistic C client library for the [Redis](https://redis.io/) database. > > It is minimalistic because it just adds minimal support for the protocol, but > at the same time it uses a high level printf-alike API in order to make it > much higher level than otherwise suggested by its minimal code base and the > lack of explicit bindings for every Redis command. > > Apart from supporting sending commands and receiving replies, it comes with > a reply parser that is decoupled from the I/O layer. It > is a stream parser designed for easy reusability, which can for instance be used > in higher level language bindings for efficient reply parsing. > > Hiredis only supports the binary-safe Redis protocol, so you can use it with any > Redis version >= 1.2.0. > > The library comes with multiple APIs. There is the > *synchronous API*, the *asynchronous API* and the *reply parsing API*. As of `1.3.0` there is no stable release URL, just the GitHub release archive.
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.