v1.44.0

• 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

• Add new experimental LSP support under buf beta lsp.

v1.42.0

• 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

• 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

• 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

• 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

• 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

• 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

• 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

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