Protorip
sign in
dashboard
---
site: protos.rip
page: compatibility
---
                                    __ 
  _________  ____ ___  ____  ____ _/ /_
 / ___/ __ \/ __ `__ \/ __ \/ __ `/ __/
/ /__/ /_/ / / / / / / /_/ / /_/ / /_  
\___/\____/_/ /_/ /_/ .___/\__,_/\__/  
                   /_/

# buf cli compatibility

works with buf cli >= v1.32.0. we recommend >= v1.46.0 for all workflows listed here.
protorip requires v2 configuration files and b5 dependency hashes. v1 configurations and b4 hashes are not supported.

## version requirements

buf cli versionsupported workflows and caveats
v1.32.0 to v1.35.xpublishing, dependency management, builds, and local code generation. sign in with an API key using `--token-stdin`; before v1.35.0, also pass `--username <your-protorip-username>`. create modules in the dashboard or with `buf push --create`. browser login and stable module, label, and commit management commands are not available.
v1.36.0 to v1.45.xadds browser login and `buf registry module`, `buf registry label`, and `buf registry commit` management commands. `buf registry whoami` is not available.
v1.46.0 and later (recommended)adds `buf registry whoami protos.rip`, covering all workflows listed here. from v1.47.0, label and commit commands also use `buf registry module label` and `buf registry module commit`.

## configuration requirements

use `version: v2` in `buf.yaml`. `buf dep update` writes a v2 `buf.lock` with `b5:` dependency digests.
if your project uses v1 configuration, run `buf config migrate` against your existing registry before switching module names and dependencies to `protos.rip`. then run `buf dep update` against protorip. CLI version and configuration version are separate requirements: upgrading the CLI alone does not migrate v1 configuration.
unfamiliar with buf cli? check out the [official docs](https://buf.build/docs/cli/) first.

## what works

### dependencies

resolve, lock, and build against remote dependencies.
```yaml
deps:
  - protos.rip/acme/petapis
```
```bash
buf dep update
buf dep graph
buf build
buf generate
```

### auth

sign in via browser or [api key](/dashboard) to publish modules or access private modules.
```bash
buf registry login protos.rip  # browser flow
echo $PROTORIP_TOKEN | buf registry login protos.rip --token-stdin  # ci / headless
buf registry whoami protos.rip
```

### publishing

create a module and push commits (on `main` by default, or tagged with `--label`).
```bash
buf registry module create protos.rip/scope/module
buf push
buf push --label v1.0.0
```

### module and label management

full management of modules, labels, and commits.
```bash
buf registry module create / info / update / delete / deprecate / undeprecate
buf registry label info / list / archive / unarchive
buf registry commit list / info
```

## not supported

remote code generation (`buf generate` with remote plugins) — not supported. use local plugins instead.
alpha/beta CLI features: `buf alpha registry token` (use the dashboard for API keys), `buf beta registry webhook`, `buf registry sdk info`.
cross-registry dependencies: buf has experimental cross-registry federation but relies on a hardcoded allowlist that does not include protos.rip. ensure all modules in your dependency chain are published to protos.rip. we maintain a handful of well-known [curated mirrors](/registry) that should meet most needs.

## compatibility target

protos.rip implements [`bufbuild/registry-proto`](https://github.com/bufbuild/registry-proto) (the BSR protocol) v1 stable services. some other non-stable services are provided for buf cli compatibility.
end-to-end compatibility checked with buf cli v1.32.0, v1.36.0, and v1.46.0 (october 2026).
[compare Protorip and buf.build BSR](/compare/buf) for pricing and product differences.
[← Back](/)