Envoy's Bazel module registry.
It holds bzlmod modules used by Envoy and related Envoy projects when they are not available in the Bazel Central Registry or require Envoy-specific patches.
All versions in this registry carry an .envoy suffix to distinguish them from BCR versions.
Add the registry to your .bazelrc, ahead of the BCR:
common --registry=https://raw.githubusercontent.com/envoyproxy/bazel-registry/main
common --registry=https://bcr.bazel.build
Then depend on modules as normal, for example:
bazel_dep(name = "nghttp2", version = "1.66.0.envoy")Follows the standard Bazel registry layout: bazel_registry.json at the root and one directory per module under modules/, each containing metadata.json and one directory per version with MODULE.bazel and source.json plus optional patches/ and overlay/.
Published module versions are immutable. The published baseline is the latest GitHub release tag for this repository, and every {module, version} present at that tag is treated as published.
Between publishes, each module may carry at most one unpublished version. If multiple unpublished versions accumulate for the same module, the prune workflow removes the older unpublished versions and keeps only the most recently appended version from that module's metadata.json.