chore(deps): update dependency @bufbuild/buf to v1.32.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@bufbuild/buf	1.27.0 -> 1.32.2

---

Release Notes

bufbuild/buf (@​bufbuild/buf)

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.

v1.30.0

Compare Source

• Update buf generate so it populates the recently-added
  source_file_descriptors
  field of the CodeGeneratorRequest message. This provides the plugin with access to options
  that are configured to only be retained in source and not at runtime (via
  field option).
  Descriptors in the proto_file field will not include any options configured this way
  for the files named in file_to_generate field.
• Add --exclude-source-retention-options flag to buf build, which
  causes options configured to only be retained in source to be stripped
  from the output descriptors.

v1.29.0

Compare Source

• Add support for yaml format. All commands that take image inputs, output images,
  or convert between message formats, now take yaml as a format, in addition to
  the existing binpb and txtpb formats. Some examples:
  • buf build -o image.yaml
  • buf ls-files image.yaml
  • buf convert --type foo.Bar --from input.binpb --to output.yaml
• The yaml and json formats now accept two new options: use_proto_names and
  use_enum_numbers. This affects output serialization. Some examples:
  • buf convert --type foo.Bar --from input.binpb --to output.yaml#use_proto_names=true
  • buf convert --type foo.Bar --from input.binpb --to -#format=yaml,use_enum_numbers=true
• Fix issue where buf format would inadvertently mangle files that used
  the expanded Any syntax
  in option values.

v1.28.1

Compare Source

• The buf curl command has been updated to support the use of multiple schemas.
  This allows users to specify multiple --schema flags and/or to use both --schema
  and --reflect flags at the same time. The result is that additional sources can
  be consulted to resolve an element. This can be useful when the result of an RPC
  contains extensions or values in google.protobuf.Any messages that are not defined
  in the same schema that defines the RPC service.
• Fix issue where buf lint incorrectly reports error when (buf.validate.field).required
  is set for an optional field in proto3.

v1.28.0

Compare Source

• Add lint rules for protovalidate. buf lint
  will now verify that your protovalidate rules are valid. A single rule PROTOVALIDATE has been
  added to the DEFAULT group - given that protovalidate is net new, this does not represent
  a breaking change.
• Update buf beta price with the latest pricing information.
• Display a warning when reading a buf.lock with dependencies with b1 or b3 digests. b1 and b3
  digests will be deprecated in a future version. Run buf mod update to update dependency digests.

v1.27.2

Compare Source

• Fix issue where buf build and other commands may fail when handling certain
  archives created on macOS that contain files with extended attributes.

v1.27.1

Compare Source

• Fix issue in v1.27.0 where --path did not work with workspaces under certain scenarios.

---

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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2043388

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR