---

site: protos.rip

page: changelog

---

        __                           __           
  _____/ /_  ____ _____  ____ ____  / /___  ____ _
 / ___/ __ \/ __ `/ __ \/ __ `/ _ \/ / __ \/ __ `/
/ /__/ / / / /_/ / / / / /_/ /  __/ / /_/ / /_/ / 
\___/_/ /_/\__,_/_/ /_/\__, /\___/_/\____/\__, /  
                      /____/             /____/

# changelog

product updates, CLI workflows, and registry changes on `protos.rip`.

## coming next

>expanding the [remote plugin catalog](/plugins) across Python, Rust, Swift, Java, and Kotlin
>generated SDK registries for Go and npm so consumer repos can install pre-compiled clients without running `buf generate`

## 2026-11-12: docs search, license detection, and org invites

>added commit-scoped search to module documentation pages
>added Protobuf extensions and applied annotations to generated schema docs
>added automatic open-source license detection on public modules
>added email invitations for organisation teams in the [dashboard](/dashboard)

## 2026-11-10: remote code generation

until now, migrating a project to `protos.rip` meant hosting modules here while running `protoc` plugins locally or pointing `buf.gen.yaml` at upstream remote plugins.

you can now run `buf generate` directly against hosted community plugins on `protos.rip`, with no local compilers or language runtimes to install in dev or CI:

```diff  version: v2  plugins:-   - remote: buf.build/protocolbuffers/go:v1.36.12+   - remote: protos.rip/protocolbuffers/go:v1.36.12      out: gen/go      opt: paths=source_relative-   - remote: buf.build/bufbuild/es:v2.16.0+   - remote: protos.rip/bufbuild/es:v2.16.0      out: web/src/gen```

>started populating remote plugin support with over 100 validated releases across Go and TypeScript/JavaScript plugins targeting Buf `<scope>/<plugin>` parity
>launched the searchable [plugin registry](/plugins) to inspect supported plugin versions, alongside search on the [module registry](/registry)
>repeat generation requests are cached automatically and cost nothing on any plan, with fair-use limits that never cut off paid plans or add overage charges (see [remote generation](/remote-generation) and the [release post](/blog/remote-code-generation))

## 2026-11-04: team management and module deprecation

>added self-serve team management in the [dashboard](/dashboard) to review org members and manage access
>added `buf registry module deprecate` and `undeprecate` support, surfacing deprecation notices to downstream consumers during `buf dep update`

## 2026-10-30: flat team pricing

>updated Team pricing to $49/month ($490/year) with unlimited private modules, types, and members, alongside Solo at $9/month and free [open-source teams](/oss)

## 2026-04: initial build (`protos.rip`)

built the core `protos.rip` registry around the open BSR protocol for `buf` CLI (`>= v1.32.0`) and `v2` configs:

```bash
buf registry login protos.rip
buf push
buf dep update
buf build
```

>module publishing, `buf.lock` dependency locking, labels, commits, and interactive CLI or API-key auth
>public [registry](/registry) and web schema browser with rendered `README` files, `.proto` file trees, commit/label history, and generated package docs at `protos.rip/<scope>/<module>`
>automatic syncing for core public modules (`googleapis/googleapis`, `bufbuild/protovalidate`, `envoyproxy/protoc-gen-validate`, `grpc-ecosystem/grpc-gateway`, and `protocolbuffers/wellknowntypes`) so projects can migrate `buf.yaml` without cross-registry errors

for supported CLI versions and workflows, read the [CLI compatibility guide](/compatibility) or the [founding post](/blog/why-protorip).