fix(deps): update module github.com/bufbuild/buf to v1.33.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/bufbuild/buf	v1.30.0 -> v1.33.0

---

Release Notes

bufbuild/buf (github.com/bufbuild/buf)

v1.33.0

Compare Source

• Allow user to override --source-control-url and --create-default-label when using
  --git-metadata with buf push.
• Fix buf push --git-metadata when local tags point to different objects than
  the remote tags.
• Fix issue where comment ignores were not respected for PROTOVALIDATE lint rule violations.
• Add buf beta registry label {create,get,list} to replace buf beta registry {draft, tag}
  commands.
• Update buf beta commit {get,list} command outputs to display create time and stop
  displaying associated tags.
• Change the behavior of buf beta commit list <buf.build/owner/repository> when the
  reference is empty. It now lists commits in the repository instead of listing commits
  of the default label.
• Update output of buf format to canonicalize the punctuation used in message literals
  in option values. The output now always uses { and } instead of < and >; it
  adds : separators between field names and message values if the source omitted them,
  and it removes unnecessary separators between fields (, and ; are allowed, but
  neither is needed).
• Update buf format -w so that it does not touch files whose contents don't actually
  change. This eliminates noisy notifications to file-system-watcher tools that are
  watching the directory that contains proto sources.
• Update buf generate to work with plugins provided by protoc for versions v24.0
  to v25.3. Editions support was experimental in these releases, and the plugins
  advertise incomplete support for editions, which triggers buf to report an error.
  With this fix, these plugins can be used again as long as none of the input files use
  editions syntax.
• Add buf push --exclude-unnamed flag to exclude unnamed modules when pushing to the BSR.

v1.32.2

Compare Source

• Update buf generate to warn instead of error when proto3 optional is required but not
  supported by a plugin.

v1.32.1

Compare Source

• 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 unintended behavior change
  that was introduced in v1.32.0.
• Add module input for protoc-gen-buf-lint and protoc-gen-buf-breaking to allow
  users to specify the module for v2 configuration files.

v1.32.0

Compare Source

• Add version v2 for buf.yaml and buf.gen.yaml configuration files.
• Add buf config migrate to migrate configuration files to the latest version (now v2).
• Move buf mod init to buf config init. buf mod init is now deprecated.
• Move buf mod ls-lint-rules to buf config ls-lint-rules. buf mod ls-lint-rules is now
  deprecated.
• Move buf mod ls-breaking-rules to buf config ls-breaking-rules. buf mod ls-breaking-rules
  is now deprecated.
• Move buf mod prune to buf dep prune. buf mod prune is now deprecated.
• Move buf mod update to buf dep update. buf mod update is now deprecated.
• Move buf mod {clear-cache,cc} to buf registry cc. buf mod {clear-cache,cc} is now
  deprecated.
• Move buf beta graph to stable as buf dep graph.
• Change the default visibility of 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.
• Add buf push --label, which allows users to set labels when pushing new commits to the BSR.
• Add buf push --source-control-url, which allows users to associate commits pushed to the BSR
  with a URL to a source code repository.
• Add buf push --create-default-label, which allows users to set a default label for a repository
  when calling buf push --create.
• Add buf push --git-metadata, which automatically sets appropriate --label,
  --source-control-url, and --create-default-label flags based on the current Git repository.
• Add buf convert --validate to apply protovalidate
  rules to incoming messages specified with --from.
• Deprecate buf mod open.
• Delete buf beta migrate-v1beta1 This is now replaced with buf config migrate.
• Add buf registry sdk version to get the version of a Generated SDK for a module and plugin.
• Add buf beta registry archive and buf beta registry unarchive commands for archiving and
  unarchiving labels on the BSR.
• Add support for Protobuf Editions. This allows 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.
• Update 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:
    1. FIELD_SAME_CARDINALITY in the FILE and PACKAGE categories.
    2. FIELD_WIRE_COMPATIBLE_CARDINALITY in the WIRE category.
    3. 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.
  • Add to the existing 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:
    1. 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.
    2. FIELD_SAME_UTF8_VALIDATION catches changes to the utf8_validation feature, which
       controls validation of string values.
    3. ENUM_SAME_TYPE catches changes to an enum's type, open vs. closed.
• Add support for extensions to 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.
• Add support for top-level extensions to buf lint. It previously only checked extensions that
  were defined inside of messages.
• Add a new 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.

v1.31.0

Compare Source

• Update dependencies.

v1.30.1

Compare Source

• Fix issue where 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 32 additional dependencies were updated

Details:

Package	Change
github.com/grpc-ecosystem/grpc-gateway/v2	v2.19.1 -> v2.20.0
golang.org/x/tools	v0.20.0 -> v0.22.0
google.golang.org/genproto/googleapis/api	v0.0.0-20240506185236-b8a5c65736ae -> v0.0.0-20240604185151-ef581f913117
google.golang.org/genproto/googleapis/rpc	v0.0.0-20240506185236-b8a5c65736ae -> v0.0.0-20240604185151-ef581f913117
google.golang.org/grpc	v1.63.2 -> v1.64.0
google.golang.org/protobuf	v1.34.1 -> v1.34.2
buf.build/gen/go/bufbuild/protovalidate/protocolbuffers/go	v1.33.0-20240221180331-f05a6f4403ce.1 -> v1.34.1-20240508200655-46a4cf4ba109.1
connectrpc.com/connect	v1.15.0 -> v1.16.2
github.com/bufbuild/protocompile	v0.9.0 -> v0.14.0
github.com/bufbuild/protovalidate-go	v0.6.0 -> v0.6.2
github.com/bufbuild/protoyaml-go	v0.1.8 -> v0.1.9
github.com/cncf/xds/go	v0.0.0-20231128003011-0fa0005c9caa -> v0.0.0-20240318125728-8a4994d93e50
github.com/cpuguy83/go-md2man/v2	v2.0.3 -> v2.0.4
github.com/distribution/reference	v0.5.0 -> v0.6.0
github.com/docker/cli	v25.0.4+incompatible -> v26.1.4+incompatible
github.com/docker/docker	v25.0.5+incompatible -> v26.1.4+incompatible
github.com/docker/docker-credential-helpers	v0.8.1 -> v0.8.2
github.com/go-logr/logr	v1.4.1 -> v1.4.2
github.com/gofrs/uuid/v5	v5.0.0 -> v5.2.0
github.com/google/go-containerregistry	v0.19.0 -> v0.19.1
github.com/google/pprof	v0.0.0-20240227163752-401108e1b7e7 -> v0.0.0-20240528025155-186aa0362fba
github.com/klauspost/compress	v1.17.7 -> v1.17.8
github.com/rs/cors	v1.10.1 -> v1.11.0
go.opentelemetry.io/proto/otlp	v1.1.0 -> v1.2.0
golang.org/x/crypto	v0.22.0 -> v0.24.0
golang.org/x/exp	v0.0.0-20240222234643-814bf88cf225 -> v0.0.0-20240604190554-fc45aab8b7f8
golang.org/x/mod	v0.17.0 -> v0.18.0
golang.org/x/net	v0.24.0 -> v0.26.0
golang.org/x/oauth2	v0.19.0 -> v0.20.0
golang.org/x/sys	v0.19.0 -> v0.21.0
golang.org/x/term	v0.19.0 -> v0.21.0
golang.org/x/text	v0.14.0 -> v0.16.0