chore(deps): update bufbuild/buf docker tag to v1.30.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
bufbuild/buf	stage	minor	1.26.1 -> 1.30.1

---

Release Notes

bufbuild/buf (bufbuild/buf)

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.

v1.27.0

Compare Source

• Fix issue where buf generate --exclude-path was not properly excluding paths
  for remote modules.
• Fix issue where buf curl had a user agent that did not properly place the
  extension as a suffix.
• Update buf beta price with the latest pricing information.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.