NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #299 by repository stars
Last release today
02 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
2434 releases · first in 2019
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
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
Update buf generate to warn instead of error when proto3 optional is required but not supported by a plugin.
buf generate to warn instead of error when proto3 optional is required but not
supported by a plugin.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
Nothing published for this version
Fix archive and git inputs so that --path and --exclude-path paths are relative to the #subdir rather than the root of the input. This fixes an uninte
--path and --exclude-path paths are relative to
the #subdir rather than the root of the input. This fixes an unintended behavior change
that was introduced in v1.32.0.module input for protoc-gen-buf-lint and protoc-gen-buf-breaking to allow
users to specify the module for v2 configuration files.Nothing published for this version
Nothing published for this version
Nothing published for this version
Move buf mod init to buf config init. buf mod init is now deprecated.
v2 for buf.yaml and buf.gen.yaml configuration files.buf config migrate to migrate configuration files to the latest version (now v2).buf mod init to buf config init. buf mod init is now deprecated.buf mod ls-lint-rules to buf config ls-lint-rules. buf mod ls-lint-rules is now
deprecated.buf mod ls-breaking-rules to buf config ls-breaking-rules. buf mod ls-breaking-rules
is now deprecated.buf mod prune to buf dep prune. buf mod prune is now deprecated.buf mod update to buf dep update. buf mod update is now deprecated.buf mod {clear-cache,cc} to buf registry cc. buf mod {clear-cache,cc} is now
deprecated.buf beta graph to stable as buf dep graph.buf push --create-visibility to private when the --create
flag is set. Users are no longer required to set --create-visibility when running
buf push --create.buf push --label, which allows users to set labels when pushing new commits to the BSR.buf push --source-control-url, which allows users to associate commits pushed to the BSR
with a URL to a source code repository.buf push --create-default-label, which allows users to set a default label for a repository
when calling buf push --create.buf push --git-metadata, which automatically sets appropriate --label,
--source-control-url, and --create-default-label flags based on the current Git repository.buf convert --validate to apply protovalidate
rules to incoming messages specified with --from.buf mod open.buf beta migrate-v1beta1 This is now replaced with buf config migrate.buf registry sdk version to get the version of a Generated SDK for a module and plugin.buf beta registry archive and buf beta registry unarchive commands for archiving and
unarchiving labels on the BSR.buf to be used with sources that use edition
2023, instead of proto2 or proto3 syntax. This also updates the protoc-gen-buf-breaking and
protoc-gen-buf-lint Protobuf plugins to support files that use edition 2023.buf breaking rules to work with Protobuf Editions. To support Editions, some rules have
been deprecated and replaced with Editions-aware rules. All deprecated rules continue to work
for existing users.
FIELD_SAME_CTYPE has been replaced with FIELD_SAME_CPP_STRING_TYPE, which considers both
ctype field options and new (pb.cpp).string_type features when deciding on backwards
compatibility.FIELD_SAME_LABEL has been replaced with three rules that all check "cardinality". The new
rules can distinguish between maps and other repeated fields and between implicit and explicit
field presence. The new rules are:
FIELD_SAME_CARDINALITY in the FILE and PACKAGE categories.FIELD_WIRE_COMPATIBLE_CARDINALITY in the WIRE category.FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY in the WIRE_JSON category.FILE_SAME_JAVA_STRING_CHECK_UTF8 has been replaced with FIELD_SAME_JAVA_UTF8_VALIDATION,
which considers both the java_string_check_utf8 file option and (pb.java).utf8_validation
features when deciding on backwards compatibility.FILE_SAME_SYNTAX rule with a few related rules that can catch the same
sort of compatibility issues, but in an Editions source file that changes feature values:
MESSAGE_SAME_JSON_FORMAT and ENUM_SAME_JSON_FORMAT catch changes to the json_format
feature, which controls whether support for the JSON format is best-effort or properly
supported. When supported, the compiler performs more checks relating to field name
collisions for the JSON format as well as for FieldMask usage.FIELD_SAME_UTF8_VALIDATION catches changes to the utf8_validation feature, which
controls validation of string values.ENUM_SAME_TYPE catches changes to an enum's type, open vs. closed.buf breaking. All existing rules for fields are now applied to
extensions, except for FIELD_NO_DELETE (and its variants). There are also new
EXTENSION_NO_DELETE and PACKAGE_EXTENSION_NO_DELETE rules for catching deletions of an
extension. The new rules are not active by default in existing v1 and v1beta1
configurations, for backwards-compatibility reasons. Migrate your config to v2 to use them.buf lint. It previously only checked extensions that
were defined inside of messages.FIELD_NOT_REQUIRED lint rule that prevents use of required in proto2 files and of
features.field_presence = LEGACY_REQUIRED in Editions files. This new rule is not active by
default in existing v1 and v1beta1 configurations, for backwards-compatibility reasons.
Migrate your config to v2 to use them.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
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
Nothing published for this version
Move buf mod init to buf config init. buf mod init is now deprecated.
buf convert --validate to apply protovalidate
rules to incoming messages specified with --from.buf config migrate to migrate configuration files to the latest version (now v2).buf beta graph to stable as buf dep graph.buf mod init to buf config init. buf mod init is now deprecated.buf mod ls-lint-rules to buf config ls-lint-rules. buf mod ls-lint-rules is now deprecated.buf mod ls-breaking-rules to buf config ls-breaking-rules. buf mod ls-breaking-rules is now deprecated.buf mod prune to buf dep prune. buf mod prune is now deprecated.buf mod update to buf dep update. buf mod update is now deprecated.buf mod {clear-cache,cc} to buf registry cc. buf mod {clear-cache,cc} is now deprecated.buf mod open.buf beta migrate-v1beta1.buf registry sdk version to get the version of a Generated SDK for a module and plugin.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
- Update dependencies.
Your coding agent can read these notes before it upgrades. Set up the MCP server →