Releases: bufbuild/buf
Releases · bufbuild/buf
v1.46.0
v1.45.0
- Update
buf registry module info --format=json
to adddefault_label_name
, which provides the name of the default label of a module.
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 todot
, and adds the optionjson
, 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 yourbuf.yaml
. - Rename
DEFAULT
lint rule category toSTANDARD
. With the concept of default rules being introduced, having a category namedDEFAULT
is confusing, as while it happens that all the rules in theDEFAULT
lint category are also default rules, the name has become overloaded. As with allbuf
changes, this change is backwards-compatible: theDEFAULT
lint category continues to work, and always will. We recommend changing toSTANDARD
, however.
v1.39.0
- Fix git input handling of relative HEAD refs without branch names.
- Add
includes
key to module configurations in v2buf.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
andexcludes
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.
- If
- Allow multiple module configurations in the same v2
buf.yaml
to have the same directory path.
v1.38.0
- Add
--http3
flag tobuf curl
which forcesbuf 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 whenbuf dep update
does not find new dependencies
to update and there is no existingbuf.lock
. - Update
buf push
to push the license file or doc file (e.g.README.md
,LICENSE
) in the
same directory asbuf.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.