NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #307 by repository stars
Last release today
08 Oct 2026
Ships on a steady schedule
a new release about every 1 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
2442 releases · first in 2019
Add buf beta registry {plugin,template} {deprecate,undeprecate}.
protoc 3.19.3 support.PACKAGE_NO_IMPORT_CYCLE lint rule to detect package import cycles.buf beta registry {plugin,template} {deprecate,undeprecate}.digest, and created_at fields from the buf.lock. This will temporarily create a new commit
when pushing the same contents to an existing repository, since the ModulePin has been reduced down.--track flag to buf pushbuf beta registry commit list to allow a track to be specified.buf beta registry track {list,delete} commands.buf.Nothing published for this version
One column per quarter.
Fix issue where remote references were not correctly cached.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is our first v1.0 release candidate. This release largely concentrates on erroring for already-deprecated commands and flags.
This is our first v1.0 release candidate. This release largely concentrates on erroring for already-deprecated commands and flags.
At Buf, we take compatibility very seriously. When we say v1.0, we mean it - we hope buf will be
stable on v1 for the next decade, and if there is something we want to change, it is our responsibility to
make sure that we don't break you, not your responsibility to change because of us. We have learned
a lot about buf usage in the last two years of our beta, and have deprecated flags and commands as
we go, but for v1.0, we are removing the deprecated items to make sure we have a clean setup going forward.
All commands and flags have been printing warnings for a long time, and have an easy migration path. Simply update the command or flag, and you'll be good to go:
buf login command in favor of buf registry login.buf logout command in favor of buf registry logout.buf mod init command in favor of buf config init.--name and --dep flags in buf config init.--log-level global flag.--version from stderr to stdout.--help and help from stderr to stdout.buf.yaml, buf.gen.yaml, buf.work.yaml) is now required.buf beta config init command in favor of buf config init.buf beta mod export command in favor of buf export.buf beta mod init command in favor of buf config init.buf beta mod update command in favor of buf mod update.buf beta mod clear-cache command in favor of buf mod clear-cache.buf beta push command in favor of buf push.buf check breaking command in favor of buf breaking.buf check lint command in favor of buf lint.buf check ls-lint-checkers command in favor of buf config ls-lint-rules.buf check ls-breaking-checkers command in favor of buf config ls-breaking-rules.--file flag on buf build in favor of the --path flag.--file flag on buf lint in favor of the --path flag.--file flag on buf breaking in favor of the --path flag.--file flag on buf generate in favor of the --path flag.--file flag on buf export in favor of the --path flag.--source flag on buf build in favor of the first positional parameter.--source-config flag on buf build in favor of the --config flag.--input flag on buf lint in favor of the first positional parameter.--input-config flag on buf lint in favor of the --config flag.--input flag on buf breaking in favor of the first positional parameter.--input-config flag on buf breaking in favor of the --config flag.--against-input flag on buf breaking in favor of the --against flag.--against-input-config flag on buf breaking in favor of the --against-config flag.--input flag on buf generate in favor of the first positional parameter.--input-config flag on buf generate in favor of the --config flag.--input flag on buf ls-files in favor of the first positional parameter.--input-config flag on buf ls-files in favor of the --config flag.buf image build command in favor of buf build.buf image convert command.buf beta image convert command.buf experimental image convert command.protoc-gen-buf-check-breaking and protoc-gen-buf-check-lint, which have been moved to protoc-gen-buf-breaking and protoc-gen-buf-lint.In January 2021 (v0.34.0), protoc-gen-buf-check-breaking and protoc-gen-buf-check-lint were deprecated and scheduled for removal for v1.0. In August 2021 (v0.52.0), we began returning error for every invocation of protoc-gen-buf-check-breaking and protoc-gen-buf-check-lint. This release completes the deletion process.
The only migration necessary is to change your installation and invocation from protoc-gen-buf-check-breaking to protoc-gen-buf-breaking and protoc-gen-buf-check-lint to protoc-gen-buf-lint. These can be installed in the exact same manner, whether from GitHub Releases, Homebrew, AUR, or direct Go installation:
# instead of go get github.com/bufbuild/buf/cmd/protoc-gen-buf-check-breaking
go get github.com/bufbuild/buf/cmd/protoc-gen-buf-breaking
# instead of curl -sSL https://github.com/bufbuild/buf/releases/download/v0.57.0/protoc-gen-buf-check-breaking-Linux-x86_64
curl -sSL https://github.com/bufbuild/buf/releases/download/v0.57.0/protoc-gen-buf-breaking-Linux-x86_64
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Cascade ENUM_ZERO_VALUE_SUFFIX comment ignores from the enum level.
ENUM_ZERO_VALUE_SUFFIX comment ignores from the enum level.buf generate --output was not being respected in 0.55.0.Nothing published for this version
Nothing published for this version
Nothing published for this version
Error if version: is not set in buf.yaml. This is one of the few breaking changes we must make before v1.0 to guarantee stability for the future. If y…
version: is not set in buf.yaml. This is one of the few breaking changes we must make before v1.0 to guarantee stability for the future. If you do not have a version set, simply add version: v1beta1 to the top of your buf.yaml.BUF_TOKEN for authentication. buf will now look for a token in the BUF_TOKEN environment variable, falling back to .netrc as set via buf login.--verbose (-v) flag.--debug flag to print out debug logging.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
- Fix docker build.
Nothing published for this version
Add java_package_prefix support to managed mode.
java_package_prefix support to managed mode.:main was appended for errors containing references to modules.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix issue where buf generate --include-imports would end up generating files for certain imports twice.
buf generate --include-imports would end up generating files for certain imports twice.buf.mod and buf.yaml are present. buf.mod was briefly used as the new default name for buf.yaml, but we've reverted back to buf.yaml.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
As one of the few changes buf will ever make, protoc-gen-buf-check-breaking and protoc-gen-buf-check-lint were deprecated and scheduled for removal fo…
Return error for all invocations of protoc-gen-buf-check-breaking and protoc-gen-buf-check-lint.
As one of the few changes buf will ever make, protoc-gen-buf-check-breaking and protoc-gen-buf-check-lint were deprecated and scheduled for removal for v1.0 in January 2021. In preparation for v1.0, instead of just printing out a message notifying users of this, these commands now return an error for every invocation and will be completely removed when v1.0 is released.
The only migration necessary is to change your installation and invocation from protoc-gen-buf-check-breaking to protoc-gen-buf-breaking and protoc-gen-buf-check-lint to protoc-gen-buf-lint. These can be installed in the exact same manner, whether from GitHub Releases, Homebrew, AUR, or direct Go installation:
# instead of go get github.com/bufbuild/buf/cmd/protoc-gen-buf-check-breaking
go get github.com/bufbuild/buf/cmd/protoc-gen-buf-breaking
# instead of curl -sSL https://github.com/bufbuild/buf/releases/download/v0.52.0/protoc-gen-buf-check-breaking-Linux-x86_64
curl -sSL https://github.com/bufbuild/buf/releases/download/v0.52.0/protoc-gen-buf-breaking-Linux-x86_64
There is no change in functionality.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix issue with git LFS where a remote must be set for fetch.
Nothing published for this version
These will be considered unstable packages for the purposes of linting and breaking change detection if ignore_unstable_packages is set.
v\d+alpha and v\d+beta as packages with valid versions. These will be considered unstable packages for the purposes of linting and breaking change detection if ignore_unstable_packages is set.Your coding agent can read these notes before it upgrades. Set up the MCP server →