buf

This is the first beta release of the next generation of the Buf CLI. This beta release is being used by some of our customers to ensure we've kept compatibility, and to try some of its new features. Don't worry - the next generation of the buf CLI continues to be v1, and is completely backwards-compatible - all of your workflows will continue to work. Buf is enterprise-grade software, and we want you to be minimally impacted.

There's some exciting improvements coming in the next generation of the buf CLI, and we look forward to sharing it more widely in the coming weeks. If you'd like to be part of the private beta, email us with the subject line "Beta" and we'll be happy to talk - we'll add more users as we have capacity. While you are free to give this beta release a spin without being added to our private beta, we wouldn't recommend using it outside of our private beta just yet!

• Update dependencies.

• Fix issue where buf lint incorrectly reports an error for (buf.validate.field).repeated
  is set for a repeated validation rule.

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

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

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

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

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

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

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

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

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

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

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

• 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 buf.build/blog/remote-packages-remote-plugins-approaching-v1 for more details.
• Update buf beta price with the latest pricing information.

• Fix issue where buf beta graph would not print modules within a workspace that had no dependencies or dependents.
• Fix issue where buf beta graph would print warnings for missing dependencies that were actually present.

• Add buf beta graph to print the dependency graph for a module in DOT format.
• Various small bug fixes.

• Change default for --origin flag of buf beta studio-agent to https://buf.build

• Fix issue where locally-produced images did not have module information if the corresponding module was stored in the new cache.
• Remove buf beta registry template.
• Remove buf beta registry plugin {create,deprecate,list,undeprecate,version} and replace with buf beta registry plugin {push,delete}.
• Update buf beta price with the latest pricing information.

• Add --emit-defaults flag to buf curl to emit default values in JSON-encoded responses.
• Indent JSON-encoded responses from buf curl by default.
• Log a warning in case an import statement does not point to a file in the module, a file in a direct dependency, or a well-known type file.