tbzl.dev

tomato-bazel is a Bazel module registry and a set of reusable rules_* for the modern, hermetic, bzlmod-first workflow.

• registry.tbzl.dev — a bzlmod registry serving the tomato-bazel modules (rules_*, brand tooling, and more), fronted by a CDN over the public tomato-bazel/bazel-registry.
• static.tbzl.dev — the brand-assets CDN (marks, icons).
• tbzl.dev — this site.

Quick start

Point Bazel at the registry in your .bazelrc:

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

Then depend on any module in your MODULE.bazel:

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

See Using the registry for more, or browse all Modules.

Using the registry

Add the tomato-bazel registry 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.

Depending on a module

In MODULE.bazel:

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

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 here

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

Authoring a module

Modules are published to the registry with the rels tool (in tomato-bazel/bazel-registry), which cuts a version from a GitHub tag.

Cut a release

1. Tag the module repo at the release commit — the tag is v<version> (matching the version in its MODULE.bazel):

   git tag v0.1.0 && git push origin v0.1.0
   

   The repo (and thus the tag tarball) must be public — a registry module’s source has to be anonymously fetchable, or keyless CI can’t resolve it.

2. From a bazel-registry checkout, cut the version — rels fetches the tag tarball, computes the integrity, and writes modules/<name>/<version>/{source.json, MODULE.bazel} + upserts metadata.json:

   bazel run //tools/rels:rels -- release \
     --repo tomato-bazel/<repo> --version 0.1.0 --name <module_name>
   

3. Commit + push. registry.tbzl.dev serves the new version within about a minute.

Conventions

• Module name is the bzlmod module name (snake_case), which may differ from the repo basename — pass --name when it does.
• rels audit flags tag↔registry drift, missing CI/CHANGELOG, and dep-pin drift.

Modules

69 modules in the tomato-bazel registry. Add to your .bazelrc: common --registry=https://registry.tbzl.dev/.