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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github.com/bufbuild/buf	require	minor	v1.23.1 -> v1.28.1

---

Release Notes

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

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.

v1.26.1

Compare Source

• Fix issue where buf build -o did not properly output files with the .txtpb
  extension in Protobuf text format.

v1.26.0

Compare Source

• Add support for the --http2-prior-knowledge flag when running buf curl
  against secure "https" URLs. This can be used with gRPC servers, that only
  support HTTP/2, when used with a network (layer 4) load balancer, that does
  not support protocol negotiation in TLS handshake.

v1.25.1

Compare Source

• Fix issue where all files were being iterated over when using the --path flag.
• Fix issue where the directory . was incorrectly accepted as a value for the
  directories key in buf.work.yaml.

v1.25.0

Compare Source

• Add txtpb format to handle the Protobuf text format. and automatically recognize
  .txtpb files as Protobuf text files. The txtpb format can now be used with
  all buf commands that take images as input or output, such as build, convert,
  and curl.

v1.24.0

Compare Source

• Update buf mod update to block updates that will result in conflicting .proto
  files across dependencies.
• Replace bin format with binpb format, and support the .binpb file extension.
  .binpb is now the canonical file extension for binary-encoded Protobuf data.
  The bin format and the .bin file extension continue to be accepted.
• Remove support for go subdomain in .netrc. This was used as part of the
  remote generation alpha, which has been fully deprecated in favor of remote
  plugins and remote packages. See https://buf.build/blog/remote-packages-remote-plugins-approaching-v1
  for more details.
• 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: 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]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.