This repository was archived by the owner on Sep 19, 2025. It is now read-only.
chore(deps): update dependency @bufbuild/buf to v1.57.2 #51
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
1.36.0->1.57.2Release Notes
bufbuild/buf (@bufbuild/buf)
v1.57.2Compare Source
v1.57.1Compare Source
v1.57.0Compare Source
gitlab-code-qualityerror format to print errors in the GitLab Code Quality formatfor
buf lintandbuf breaking.source_control_urltojsonoutputs forbuf registry {module, plugin} commitcommands.v1.56.0Compare Source
buf export --allflag to include non-proto source files.buf lintwill no longer warn about uses of(buf.validate.message).disabled, as it wasremoved in protovalidate v0.14.0. Please update to protovalidate v0.14.0 or higher, using the
steps outlined in the
protovalidate release notes.
buf breaking --against-registryto work with new modules that have no commits on thedefault branch.
v1.55.1Compare Source
v1.55.0Compare Source
buf beta statstobuf stats.buf registry sdk infocommand.to run
buf breaking, ignoring new module(s).v1.54.0Compare Source
CSRcategory to breaking rules.protoc-gen-buf-breakingandprotoc-gen-buf-lint.buf generatefor empty files, files with no declared types.buf lintfor predefinedrulesvariables.buf config migrateto filter out removed rules.PROTOVALIDATElint rule.v1.53.0Compare Source
v1.52.1Compare Source
v1.52.0Compare Source
exclude_typeon a non imported package.--exclude-typeflag forbuf generatewhen an input is specified.buf lintandbuf breakingoutput even when source code info is notavailable. This allows
buf lintandbuf breakingto respectignoreandignore_onlyconfigurations when source code info is not available.
v1.51.0Compare Source
buf convertto allow for zero length forbinpb,txtpb, andyamlformats.--include-typesforbuf generate.--against-registryflag tobuf breakingthat runs breaking checks against the latestcommit on the default branch of the corresponding module in the registry.
buf generate.buf generate. Adds the ability to exclude types with the parameterexclude_typesinbuf.gen.yamland a flag--exclude-typesin the CLI.Type filters may now also be specified as plugin parameters in
buf.gen.yaml.v1.50.1Compare Source
v1.50.0Compare Source
filterfor use with git inputs. This sets the filterflag argument for the git fetch command.
v1.49.0Compare Source
buf plugin push --labelto allow pushing a plugin with a label.--digest-changes-onlyflag tobuf registry {module,plugin} commit listto filterout commits that have no digest changes.
buf plugin push --source-control-urlto allow pushing a plugin with the sourcecontrol url.
v1.48.0Compare Source
buf registry plugin {create,delete,info,update}commands to manage BSR plugins.buf beta lsp.--typeflag filter forbuf buildwhere import ordering is notdeterministic.
buf plugin pushcommand to push a plugin to the Buf Schema Registry.Only WebAssembly check plugins are supported at this time.
buf plugin updateandbuf plugin prunecommand to manage plugins in thebuf.lockfile. Only WebAssembly check plugins are supported at this time.
buf registry plugin commit {add-label,info,list,resolve}to manage BSR plugin commits.buf registry plugin label {archive,info,list,unarchive}to manage BSR plugin commits.buf registry module updatetobuf registry module settings update. Commandbuf registry module updateis now deprecated.buf lintandbuf breakingcommands.v1.47.2Compare Source
v1.47.1Compare Source
v1.47.0Compare Source
buf registry committobuf registry module commit. Commandbuf registry commitis now deprecated.buf registry labeltobuf registry module label. Commandbuf registry labelis now deprecated.v1.46.0Compare Source
buf registry whoamicommand, which checks if you are logged in to the Buf SchemaRegistry at a given domain.
v1.45.0Compare Source
buf registry module info --format=jsonto adddefault_label_name, which provides the nameof the default label of a module.
v1.44.0Compare Source
PROTOVALIDATElint rule to check example field options. Examples will be checked thatthey satisfy the field constraints, and are only present if constraints are present.
PROTOVALIDATElint rule to check predefined rules. Predefined rules will be checkedthat they compile.
.wasmfile extension to specify a path to a Wasm plugin.v1.43.0Compare Source
buf beta lsp.v1.42.0Compare Source
our launch blog post
for more details!
buf dep graph --formatflag that defaults todot, and adds the optionjson, to printthe dependency graph in JSON format.
buf formatwhere trailing comments on commas in message literals were not properlypropagated 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.0Compare Source
buf curl.v1.40.1Compare Source
buf lintwhere comment ignores in the shape of// buf:lint:ignore <RULE_ID> <extra comment>were not recognized due to the extra comment.
v1.40.0Compare Source
buf config ls-{breaking,lint}-rules. Default rules are those rules which are run if no lintor breaking rules are explicitly configured in your
buf.yaml.DEFAULTlint rule category toSTANDARD. With the concept of default rules being introduced,having a category named
DEFAULTis confusing, as while it happens that all the rules in theDEFAULTlint category are also default rules, the name has become overloaded. As with all
bufchanges, thischange is backwards-compatible: the
DEFAULTlint category continues to work, and always will. Werecommend changing to
STANDARD, however.v1.39.0Compare Source
includeskey to module configurations in v2buf.yaml, accepting a list of directories.includesis specified, a proto file is considered in the module only if it is in one of thedirectories specified.
includesandexcludeskeys are specified for a module, a proto file is consideredpart of this module if it is contained in any of the include paths and not in any of the exclude
paths.
buf.yamlto have the same directory path.v1.38.0Compare Source
--http3flag tobuf curlwhich forcesbuf curlto use HTTP/3 as the transport.a path to a module, but contained directories with modules, and the modules would not build.
buf.lockfiles whenbuf dep updatedoes not find new dependenciesto update and there is no existing
buf.lock.buf pushto push the license file or doc file (e.g.README.md,LICENSE) in thesame directory as
buf.yamlif a module does not have a license file or doc file in themodule's directory.
--pathflag for lint and breaking rules to avoid resolving all fileswithin a module. This change can result in a performance improvement for large workspaces.
v1.37.0Compare Source
STABLE_PACKAGE_NO_IMPORT_UNSTABLElint rule which disallows files from stable packagesto import files from unstable packages.
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.
This PR was generated by Mend Renovate. View the repository job log.