-
Notifications
You must be signed in to change notification settings - Fork 1
Update module github.com/bufbuild/buf to v1.58.0 - autoclosed #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
5680940 to
5a8cd45
Compare
5a8cd45 to
c9f9ca9
Compare
cd8e51a to
cc0c663
Compare
cc0c663 to
169a323
Compare
169a323 to
1010b7d
Compare
1010b7d to
1f7dcfa
Compare
1f7dcfa to
79f8d26
Compare
79f8d26 to
2da0019
Compare
2da0019 to
6e30b8b
Compare
6e30b8b to
3a869b0
Compare
3a869b0 to
5794ac0
Compare
5794ac0 to
902c2a1
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
902c2a1 to
082c9b8
Compare
082c9b8 to
e10539d
Compare
55a7ab7 to
ec60af2
Compare
ec60af2 to
3a8c952
Compare
3a8c952 to
eab77cd
Compare
eab77cd to
4927297
Compare
7143b45 to
bb96dda
Compare
|
bb96dda to
9e56417
Compare
9e56417 to
6637caf
Compare
6637caf to
30ea7ed
Compare
30ea7ed to
2268a19
Compare
2268a19 to
84dc8d0
Compare
84dc8d0 to
7ec0350
Compare
7ec0350 to
cc4f64c
Compare
This PR contains the following updates:
v1.26.1->v1.58.0Release Notes
bufbuild/buf (github.com/bufbuild/buf)
v1.58.0Compare Source
PROTOVALIDATElint rule to checkIGNORE_IF_ZERO_VALUEon fields that track presence.buf formaton fields with missing field number tags.includeandexcludepath handling for workspaces to avoid unnecessary file systemoperations. This change can result in a performance improvement for large workspaces.
--http2-prior-knowledgeflag set.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.
v1.36.0Compare Source
--list-servicesand--list-methodsflags tobuf curl, which trigger the command to listknown services or methods in the RPC schema, instead of invoking an RPC method.
cleanas a top-level option inbuf.gen.yaml, matching thebuf generate --cleanflag. Ifset to true, this will delete the directories, jar files, or zip files set to
outfor eachplugin.
buf registry loginto complete the login flow in the browser by default. This allowsusers to login with their browser and have the token automatically provided to the CLI.
buf registry organization {create, delete, info, update}commands to manage BSRorganizations. Remove
buf beta registry organizationcommands.buf registry module {create, delete, deprecate, info, undeprecate, update}commands tomanage BSR modules. Remove
buf beta registry repositorycommands.buf registry label {archive, info, list, unarchive}commands to manage BSR module labels.Remove
buf beta registry labelcommands andbuf beta registry {archive, unarchive}.buf registry commit {add-label, info, list, resolve}to manage BSR module commits. Removebuf beta registry commitcommands.v1.35.1Compare Source
refto align with thegitnotion of a ref. This allows for the useof branch names, tag names, and commit hashes.
buf builderrors with absolute path directory inputs without workspace and/ormodule configurations (e.g.
buf.yaml,buf.work.yaml) and proto file paths set to the--pathflag.v1.35.0Compare Source
buf generate --cleanflag that will delete the directories, jar files, or zip files that theplugins will write to, prior to generation. Allows cleaning of existing assets without having
to call
rm -rf.--usernameflag on and username prompt onbuf registry login. A username is no longerrequired to log in.
v1.34.0Compare Source
buf config ls-modulescommand to list configured modules.buf generatewould succeed on missing insertion points andpanic on empty insertion point files.
buf generateto allow the use of Editions syntax when doing local codegeneration by proxying to a
protocbinary (for languages where code gen isimplemented inside of
protocinstead of in a plugin: Java, C++, Python, etc).protoc_pathproperty of forbuf.gen.yaml,where the first array element is the actual path and other array elements are extra
arguments that are passed to
protoceach time it is invoked.v1.33.0Compare Source
--source-control-urland--create-default-labelwhen using--git-metadatawithbuf push.buf push --git-metadatawhen local tags point to different objects thanthe remote tags.
PROTOVALIDATElint rule violations.buf beta registry label {create,get,list}to replacebuf beta registry {draft, tag}commands.
buf beta commit {get,list}command outputs to display create time and stopdisplaying associated tags.
buf beta commit list <buf.build/owner/repository>when thereference is empty. It now lists commits in the repository instead of listing commits
of the default label.
buf formatto canonicalize the punctuation used in message literalsin option values. The output now always uses
{and}instead of<and>; itadds
:separators between field names and message values if the source omitted them,and it removes unnecessary separators between fields (
,and;are allowed, butneither is needed).
buf format -wso that it does not touch files whose contents don't actuallychange. This eliminates noisy notifications to file-system-watcher tools that are
watching the directory that contains proto sources.
buf generateto work with plugins provided by protoc for versions v24.0to v25.3. Editions support was experimental in these releases, and the plugins
advertise incomplete support for editions, which triggers
bufto report an error.With this fix, these plugins can be used again as long as none of the input files use
editions syntax.
buf push --exclude-unnamedflag to exclude unnamed modules when pushing to the BSR.v1.32.2Compare Source
buf generateto warn instead of error when proto3 optional is required but notsupported by a plugin.
v1.32.1Compare Source
--pathand--exclude-pathpaths are relative tothe
#subdirrather than the root of the input. This fixes an unintended behavior changethat was introduced in
v1.32.0.moduleinput forprotoc-gen-buf-lintandprotoc-gen-buf-breakingto allowusers to specify the module for
v2configuration files.v1.32.0Compare Source
v2forbuf.yamlandbuf.gen.yamlconfiguration files.buf config migrateto migrate configuration files to the latest version (nowv2).buf mod inittobuf config init.buf mod initis now deprecated.buf mod ls-lint-rulestobuf config ls-lint-rules.buf mod ls-lint-rulesis nowdeprecated.
buf mod ls-breaking-rulestobuf config ls-breaking-rules.buf mod ls-breaking-rulesis now deprecated.
buf mod prunetobuf dep prune.buf mod pruneis now deprecated.buf mod updatetobuf dep update.buf mod updateis now deprecated.buf mod {clear-cache,cc}tobuf registry cc.buf mod {clear-cache,cc}is nowdeprecated.
buf beta graphto stable asbuf dep graph.buf push --create-visibilitytoprivatewhen the--createflag is set. Users are no longer required to set
--create-visibilitywhen runningbuf push --create.buf push --label, which allows users to set labels when pushing new commits to the BSR.buf push --source-control-url, which allows users to associate commits pushed to the BSRwith a URL to a source code repository.
buf push --create-default-label, which allows users to set a default label for a repositorywhen calling
buf push --create.buf push --git-metadata, which automatically sets appropriate--label,--source-control-url, and--create-default-labelflags based on the current Git repository.buf convert --validateto apply protovalidaterules to incoming messages specified with
--from.buf mod open.buf beta migrate-v1beta1This is now replaced withbuf config migrate.buf registry sdk versionto get the version of a Generated SDK for a module and plugin.buf beta registry archiveandbuf beta registry unarchivecommands for archiving andunarchiving labels on the BSR.
bufto be used with sources that use edition2023, instead of proto2 or proto3 syntax. This also updates the
protoc-gen-buf-breakingandprotoc-gen-buf-lintProtobuf plugins to support files that use edition 2023.buf breakingrules to work with Protobuf Editions. To support Editions, some rules havebeen deprecated and replaced with Editions-aware rules. All deprecated rules continue to work
for existing users.
FIELD_SAME_CTYPEhas been replaced withFIELD_SAME_CPP_STRING_TYPE, which considers bothctypefield options and new(pb.cpp).string_typefeatures when deciding on backwardscompatibility.
FIELD_SAME_LABELhas been replaced with three rules that all check "cardinality". The newrules can distinguish between maps and other repeated fields and between implicit and explicit
field presence. The new rules are:
FIELD_SAME_CARDINALITYin theFILEandPACKAGEcategories.FIELD_WIRE_COMPATIBLE_CARDINALITYin theWIREcategory.FIELD_WIRE_JSON_COMPATIBLE_CARDINALITYin theWIRE_JSONcategory.FILE_SAME_JAVA_STRING_CHECK_UTF8has been replaced withFIELD_SAME_JAVA_UTF8_VALIDATION,which considers both the
java_string_check_utf8file option and(pb.java).utf8_validationfeatures when deciding on backwards compatibility.
FILE_SAME_SYNTAXrule with a few related rules that can catch the samesort of compatibility issues, but in an Editions source file that changes feature values:
MESSAGE_SAME_JSON_FORMATandENUM_SAME_JSON_FORMATcatch changes to thejson_formatfeature, 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.
FIELD_SAME_UTF8_VALIDATIONcatches changes to theutf8_validationfeature, whichcontrols validation of string values.
ENUM_SAME_TYPEcatches changes to an enum's type, open vs. closed.buf breaking. All existing rules for fields are now applied toextensions, except for
FIELD_NO_DELETE(and its variants). There are also newEXTENSION_NO_DELETEandPACKAGE_EXTENSION_NO_DELETErules for catching deletions of anextension. The new rules are not active by default in existing
v1andv1beta1configurations, for backwards-compatibility reasons. Migrate your config to
v2to use them.buf lint. It previously only checked extensions thatwere defined inside of messages.
FIELD_NOT_REQUIREDlint rule that prevents use of required in proto2 files and offeatures.field_presence = LEGACY_REQUIREDin Editions files. This new rule is not active bydefault in existing
v1andv1beta1configurations, for backwards-compatibility reasons.Migrate your config to
v2to use them.v1.31.0Compare Source
v1.30.1Compare Source
buf lintincorrectly reports an error for(buf.validate.field).repeatedis set for a repeated validation rule.
v1.30.0Compare Source
buf generateso it populates the recently-addedsource_file_descriptorsfield of the
CodeGeneratorRequestmessage. This provides the plugin with access to optionsthat are configured to only be retained in source and not at runtime (via
field option).
Descriptors in the
proto_filefield will not include any options configured this wayfor the files named in
file_to_generatefield.--exclude-source-retention-optionsflag tobuf build, whichcauses options configured to only be retained in source to be stripped
from the output descriptors.
v1.29.0Compare Source
yamlformat. All commands that take image inputs, output images,or convert between message formats, now take
yamlas a format, in addition tothe existing
binpbandtxtpbformats. Some examples:buf build -o image.yamlbuf ls-files image.yamlbuf convert --type foo.Bar --from input.binpb --to output.yamlyamlandjsonformats now accept two new options:use_proto_namesanduse_enum_numbers. This affects output serialization. Some examples:buf convert --type foo.Bar --from input.binpb --to output.yaml#use_proto_names=truebuf convert --type foo.Bar --from input.binpb --to -#format=yaml,use_enum_numbers=truebuf formatwould inadvertently mangle files that usedthe expanded
Anysyntaxin option values.
v1.28.1Compare Source
buf curlcommand has been updated to support the use of multiple schemas.This allows users to specify multiple
--schemaflags and/or to use both--schemaand
--reflectflags at the same time. The result is that additional sources canbe consulted to resolve an element. This can be useful when the result of an RPC
contains extensions or values in
google.protobuf.Anymessages that are not definedin the same schema that defines the RPC service.
buf lintincorrectly reports error when(buf.validate.field).requiredis set for an optional field in proto3.
v1.28.0Compare Source
buf lintwill now verify that your protovalidate rules are valid. A single rule
PROTOVALIDATEhas beenadded to the
DEFAULTgroup - given that protovalidate is net new, this does not representa breaking change.
buf beta pricewith the latest pricing information.buf.lockwith dependencies with b1 or b3 digests. b1 and b3digests will be deprecated in a future version. Run
buf mod updateto update dependency digests.v1.27.2Compare Source
buf buildand other commands may fail when handling certainarchives created on macOS that contain files with extended attributes.
v1.27.1Compare Source
--pathdid not work with workspaces under certain scenarios.v1.27.0Compare Source
buf generate --exclude-pathwas not properly excluding pathsfor remote modules.
buf curlhad a user agent that did not properly place theextension as a suffix.
buf beta pricewith the latest pricing information.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.