---

site: protos.rip

page: changelog

---

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

# changelog

new features, workflow improvements, and plugin rollouts on `protos.rip`.

## coming next

we’re currently testing generated sdk registries for npm and go. soon you’ll be able to `npm install` or `go get` pre-compiled protobuf and connect client packages directly from `protos.rip` (supporting both `@protorip/*` and `@buf/*` scopes for drop-in migration) without running `buf generate` in consumer repos.

we’re also continuing to expand the [remote plugin catalog](/plugins) with additional versions and language runtimes across python, rust, swift, java, and kotlin.

## november 10, 2026: remote code generation is live

until today, migrating a project to `protos.rip` meant moving your module hosting over (`buf.yaml`), while still either 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 development 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```

we’ve populated the [plugin registry](/plugins) with over 100 validated releases across the core go and typescript/javascript ecosystems (`protocolbuffers/go`, `connectrpc/go`, `grpc/go`, `grpc-ecosystem/gateway`, `grpc-ecosystem/openapiv2`, `bufbuild/validate-go`, `bufbuild/es`, `connectrpc/es`, `connectrpc/query-es`, `community/stephenh-ts-proto`, and `community/timostamm-protobuf-ts`), with more community plugins and versions rolling out over the coming days.

cached generation results are unlimited and free on every plan. when schemas or plugin options change, paid and oss plans run plugins in parallel with generous monthly allowances and no overage charges. see [remote code generation](/remote-generation) for how execution and caching work.

## october 22, 2026: team member management & module deprecation

we’ve added self-serve team management to the [dashboard](/dashboard) so organisation admins can invite teammates, manage pending invites, and review member access directly from organisation settings.

on the cli side, `buf registry module deprecate` now stores explicit deprecation notices and surfaces them to downstream consumers during `buf dep update`, making it easier to sunset old schema modules cleanly across repositories.

## september 14, 2026: web schema explorer & generated package docs

every public module on `protos.rip` now gets a full web view at `protos.rip/<scope>/<module>`.

when you push a commit, protorip automatically renders your module’s `README`, detects its open-source license, and generates browsable documentation for every protobuf package, service, rpc method, message, and enum. you can also step through the `.proto` file tree and inspect commit and label history directly in the browser.

## july 28, 2026: core public modules (`googleapis`, `protovalidate`, `grpc-gateway`)

almost every non-trivial protobuf schema depends on upstream definitions like `google/api/annotations.proto` or `buf/validate/validate.proto`. because the `buf` cli doesn’t allow mixing registries in a dependency graph by default, migrating your own modules requires those foundational packages to live on the same registry.

we now maintain the core public modules on `protos.rip` under their standard paths:

>`protos.rip/googleapis/googleapis`
>`protos.rip/bufbuild/protovalidate`
>`protos.rip/envoyproxy/protoc-gen-validate`
>`protos.rip/grpc-ecosystem/grpc-gateway`
>`protos.rip/protocolbuffers/wellknowntypes`

new upstream releases sync automatically, so migrating a project’s `buf.yaml` is now a simple find-and-replace from `buf.build` to `protos.rip`. browse all available packages in the [public registry](/registry).

## june 9, 2026: launching protorip (`protos.rip`)

we launched `protos.rip` to give engineering teams a drop-in protobuf schema registry for the `buf` cli with flat, predictable pricing instead of per-type metering.

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

out of the box, `protos.rip` works with your existing `buf` cli (`>= v1.32.0`) and `v2` configuration files:

>publish and version public and private modules with `buf push` and reproducible `buf.lock` dependency locking
>sign in interactively with `buf registry login protos.rip` or use scoped api keys in ci
>manage modules, labels, and commits from the cli or web dashboard
>flat-rate [solo ($9/mo) and team ($49/mo) plans](/pricing) with unlimited private modules and types, plus free team accounts for [open-source projects](/oss)

read [why we built protorip](/blog/why-protorip) or check the [cli compatibility guide](/compatibility) to get started.