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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
bufbuild/buf	stage	minor	1.25.0 -> 1.47.2

---

Release Notes

bufbuild/buf (bufbuild/buf)

v1.47.2

Compare Source

• Update the patch version to resolve NPM packaging issues. No command updates or user changes.

v1.47.1

Compare Source

• Update the patch version to resolve NPM packaging issues. No command updates or user changes.

v1.47.0

Compare Source

• Move buf registry commit to buf registry module commit. Command
  buf registry commit is now deprecated.
• Move buf registry label to buf registry module label. Command
  buf registry label is now deprecated.

v1.46.0

Compare Source

• Add buf registry whoami command, which checks if you are logged in to the Buf Schema
  Registry at a given domain.

v1.45.0

Compare Source

• Update buf registry module info --format=json to add default_label_name, which provides the name
  of the default label of a module.

v1.44.0

Compare Source

• Update the PROTOVALIDATE lint rule to check example field options. Examples will be checked that
  they satisfy the field constraints, and are only present if constraints are present.
• Update the PROTOVALIDATE lint rule to check predefined rules. Predefined rules will be checked
  that they compile.
• Add support for a WebAssembly (Wasm) runtime for custom lint and breaking changes plugins. Use the
  .wasm file extension to specify a path to a Wasm plugin.

v1.43.0

Compare Source

• Add new experimental LSP support under buf beta lsp.

v1.42.0

Compare Source

• Add support for custom lint and breaking change plugins. See
  our launch blog post
  for more details!
• Add buf dep graph --format flag that defaults to dot, and adds the option json, to print
  the dependency graph in JSON format.
• Fix bugs in buf format where trailing comments on commas in message literals were not properly
  propagated to the formatted proto, empty message literals were not properly indented, and
  compound strings in options added an extra newline before trailing commas.

v1.41.0

Compare Source

• Add HTTP/3 support for gRPC with buf curl.
• Fix issue where errors from protoc plugins may be overwritten when executing plugins in parallel.

v1.40.1

Compare Source

• Fix issue with buf lint where comment ignores in the shape of // buf:lint:ignore <RULE_ID> <extra comment>
  were not recognized due to the extra comment.

v1.40.0

Compare Source

• Add concept of a default lint or breaking rule, which is printed out as a property when running
  buf config ls-{breaking,lint}-rules. Default rules are those rules which are run if no lint
  or breaking rules are explicitly configured in your buf.yaml.
• Rename DEFAULT lint rule category to STANDARD. With the concept of default rules being introduced,
  having a category named DEFAULT is confusing, as while it happens that all the rules in the DEFAULT
  lint category are also default rules, the name has become overloaded. As with all buf changes, this
  change is backwards-compatible: the DEFAULT lint category continues to work, and always will. We
  recommend changing to STANDARD, however.

v1.39.0

Compare Source

• Fix git input handling of relative HEAD refs without branch names.
• Add includes key to module configurations in v2 buf.yaml, accepting a list of directories.
  • If includes is specified, a proto file is considered in the module only if it is in one of the
    directories specified.
  • If both includes and excludes keys are specified for a module, a proto file is considered
    part of this module if it is contained in any of the include paths and not in any of the exclude
    paths.
• Allow multiple module configurations in the same v2 buf.yaml to have the same directory path.

v1.38.0

Compare Source

• Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
• Fix issue with directory inputs for v2 workspaces where the specified directory was not itself
  a path to a module, but contained directories with modules, and the modules would not build.
• Stop creating empty buf.lock files when buf dep update does not find new dependencies
  to update and there is no existing buf.lock.
• Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the
  same directory as buf.yaml if a module does not have a license file or doc file in the
  module's directory.
• Fix constraints of --path flag for lint and breaking rules to avoid resolving all files
  within a module. This change can result in a performance improvement for large workspaces.

v1.37.0

Compare Source

• Add STABLE_PACKAGE_NO_IMPORT_UNSTABLE lint rule which disallows files from stable packages
  to import files from unstable packages.
• Fix plugin push failures when pushing an image built with containerd image store.

v1.36.0

Compare Source

• Add --list-services and --list-methods flags to buf curl, which trigger the command to list
  known services or methods in the RPC schema, instead of invoking an RPC method.
• Add clean as a top-level option in buf.gen.yaml, matching the buf generate --clean flag. If
  set to true, this will delete the directories, jar files, or zip files set to out for each
  plugin.
• Fix git input handling of annotated tags.
• Update buf registry login to complete the login flow in the browser by default. This allows
  users to login with their browser and have the token automatically provided to the CLI.
• Add buf registry organization {create, delete, info, update} commands to manage BSR
  organizations. Remove buf beta registry organization commands.
• Add buf registry module {create, delete, deprecate, info, undeprecate, update} commands to
  manage BSR modules. Remove buf beta registry repository commands.
• Add buf registry label {archive, info, list, unarchive} commands to manage BSR module labels.
  Remove buf beta registry label commands and buf beta registry {archive, unarchive}.
• Add buf registry commit {add-label, info, list, resolve} to manage BSR module commits. Remove
  buf beta registry commit commands.

v1.35.1

Compare Source

• Fix the git input parameter ref to align with the git notion of a ref. This allows for the use
  of branch names, tag names, and commit hashes.
• Fix unexpected buf build errors with absolute path directory inputs without workspace and/or
  module configurations (e.g. buf.yaml, buf.work.yaml) and proto file paths set to the --path flag.

v1.35.0

Compare Source

• Add buf generate --clean flag that will delete the directories, jar files, or zip files that the
  plugins will write to, prior to generation. Allows cleaning of existing assets without having
  to call rm -rf.
• Deprecate --username flag on and username prompt on buf registry login. A username is no longer
  required to log in.

v1.34.0

Compare Source

• Add buf config ls-modules command to list configured modules.
• Fix issue where buf generate would succeed on missing insertion points and
  panic on empty insertion point files.
• Update buf generate to allow the use of Editions syntax when doing local code
  generation by proxying to a protoc binary (for languages where code gen is
  implemented inside of protoc instead of in a plugin: Java, C++, Python, etc).
• Allow use of an array of strings for the protoc_path property of for buf.gen.yaml,
  where the first array element is the actual path and other array elements are extra
  arguments that are passed to protoc each time it is invoked.

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.

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.

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.

---

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.