Protorip
---
site: protos.rip
page: changelog
---

# changelog

keep up with updates to `buf` CLI support, registry and dashboard changes, and new features on `protos.rip`.

## in development

  • >expanding [remote plugin](/plugins) support for Python, Rust, Swift, Java, and Kotlin ecosystems
  • >generated SDK registries for Go and npm
  • >added [/llms.txt](/llms.txt) and site discovery links for coding agents migrating or consuming modules and remote plugins
  • >you can now search documentation from a module’s registry page instead of having to visit a docs page first

## 2026-11-19: Google sign-in and account linking

  • >enabled Google OAuth registration and sign-in
  • >you can now link your Google and GitHub accounts if you sign in on both providers with the same primary email

## 2026-11-14: more flexible organisation creation and management

we’ve removed the need to claim a personal organisation on sign-up, so you can join a team organisation directly without setting up a username or accidentally squatting your organisation’s name.
  • >you can now claim an additional free solo organisation when you upgrade an existing one to the paid solo plan
  • >you can now upgrade an existing solo organisation to a team organisation

## 2026-11-13: teams, module roles, and scoped tokens

you can now manage access to modules within your protorip organisation with teams and role assignments; read more in the [release post](/blog/teams-module-roles-and-scoped-tokens).
  • >added role assignments for enforcing your team’s access permissions to modules
  • >added organisation teams which let you manage role assignments for a group of users together
  • >improved management of API tokens with separate pages to manage scoped personal tokens and service tokens belonging to an organisation

## 2026-11-12: docs search and license detection

  • >added symbol search to module documentation pages
  • >added Protobuf extensions and applied annotations to generated schema docs
  • >added automatic open-source license detection on public modules
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```

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

  • >added self-serve team member 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-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
  • >[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).