Using the registry

Point Bazel at the tomato-bazel registry and depend on any published module — every version is immutable and integrity-checked.

Add the registry

Add it to your .bazelrc, ahead of the BCR:

common --registry=https://registry.tbzl.dev/
common --registry=https://bcr.bazel.build/

Bazel consults registries left-to-right, so a module present in both resolves from registry.tbzl.dev first, falling back to the BCR.

Depend on a module

In MODULE.bazel:

bazel_dep(name = "rules_tomato", version = "0.1.1")

Pins resolve to an immutable module version — registry.tbzl.dev/modules/<name>/<version>/ (MODULE.bazel + source.json). Version files are cached hard by the CDN; the mutable index (metadata.json) is served with a short TTL, so a freshly-published version is visible within about a minute.

What’s published

The Modules reference lists every module and its versions. Sources live in the public tomato-bazel/bazel-registry repo.