fix(deps): update module github.com/bufbuild/buf to v1.32.1 #1056
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.30.0
->v1.32.1
Release Notes
bufbuild/buf (github.com/bufbuild/buf)
v1.32.1
Compare Source
--path
and--exclude-path
paths are relative tothe
#subdir
rather than the root of the input. This fixes an unintended behavior changethat was introduced in
v1.32.0
.module
input forprotoc-gen-buf-lint
andprotoc-gen-buf-breaking
to allowusers to specify the module for
v2
configuration files.v1.32.0
Compare Source
v2
forbuf.yaml
andbuf.gen.yaml
configuration files.buf config migrate
to migrate configuration files to the latest version (nowv2
).buf mod init
tobuf config init
.buf mod init
is now deprecated.buf mod ls-lint-rules
tobuf config ls-lint-rules
.buf mod ls-lint-rules
is nowdeprecated.
buf mod ls-breaking-rules
tobuf config ls-breaking-rules
.buf mod ls-breaking-rules
is now deprecated.
buf mod prune
tobuf dep prune
.buf mod prune
is now deprecated.buf mod update
tobuf dep update
.buf mod update
is now deprecated.buf mod {clear-cache,cc}
tobuf registry cc
.buf mod {clear-cache,cc}
is nowdeprecated.
buf beta graph
to stable asbuf dep graph
.buf push --create-visibility
toprivate
when the--create
flag is set. Users are no longer required to set
--create-visibility
when runningbuf 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 BSRwith a URL to a source code repository.
buf push --create-default-label
, which allows users to set a default label for a repositorywhen 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 protovalidaterules to incoming messages specified with
--from
.buf mod open
.buf beta migrate-v1beta1
This is now replaced withbuf config migrate
.buf registry sdk version
to get the version of a Generated SDK for a module and plugin.buf beta registry archive
andbuf beta registry unarchive
commands for archiving andunarchiving labels on the BSR.
buf
to be used with sources that use edition2023, instead of proto2 or proto3 syntax. This also updates the
protoc-gen-buf-breaking
andprotoc-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 havebeen deprecated and replaced with Editions-aware rules. All deprecated rules continue to work
for existing users.
FIELD_SAME_CTYPE
has been replaced withFIELD_SAME_CPP_STRING_TYPE
, which considers bothctype
field options and new(pb.cpp).string_type
features when deciding on backwardscompatibility.
FIELD_SAME_LABEL
has been replaced with three rules that all check "cardinality". The newrules can distinguish between maps and other repeated fields and between implicit and explicit
field presence. The new rules are:
FIELD_SAME_CARDINALITY
in theFILE
andPACKAGE
categories.FIELD_WIRE_COMPATIBLE_CARDINALITY
in theWIRE
category.FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY
in theWIRE_JSON
category.FILE_SAME_JAVA_STRING_CHECK_UTF8
has been replaced withFIELD_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 samesort of compatibility issues, but in an Editions source file that changes feature values:
MESSAGE_SAME_JSON_FORMAT
andENUM_SAME_JSON_FORMAT
catch changes to thejson_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 theutf8_validation
feature, whichcontrols 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 toextensions, except for
FIELD_NO_DELETE
(and its variants). There are also newEXTENSION_NO_DELETE
andPACKAGE_EXTENSION_NO_DELETE
rules for catching deletions of anextension. The new rules are not active by default in existing
v1
andv1beta1
configurations, for backwards-compatibility reasons. Migrate your config to
v2
to use them.buf lint
. It previously only checked extensions thatwere defined inside of messages.
FIELD_NOT_REQUIRED
lint rule that prevents use of required in proto2 files and offeatures.field_presence = LEGACY_REQUIRED
in Editions files. This new rule is not active bydefault in existing
v1
andv1beta1
configurations, for backwards-compatibility reasons.Migrate your config to
v2
to use them.v1.31.0
Compare Source
v1.30.1
Compare Source
buf lint
incorrectly reports an error for(buf.validate.field).repeated
is set for a repeated validation rule.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.