Update module github.com/bufbuild/buf to v1.37.0

Open renovate[bot] opened this issue 1 year ago • 1 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/bufbuild/buf	`v1.30.0` -> `v1.37.0`

Release Notes

bufbuild/buf (github.com/bufbuild/buf)

`v1.37.0`

Compare Source

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`

Compare Source

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.

`v1.35.1`

Compare Source

Fix the git input parameter ref to align with the git notion of a ref. This allows for the use of branch names, tag names, and commit hashes.
Fix unexpected buf build errors with absolute path directory inputs without workspace and/or module configurations (e.g. buf.yaml, buf.work.yaml) and proto file paths set to the --path flag.

`v1.35.0`

Compare Source

Add buf generate --clean flag that will delete the directories, jar files, or zip files that the plugins will write to, prior to generation. Allows cleaning of existing assets without having to call rm -rf.
Deprecate --username flag on and username prompt on buf registry login. A username is no longer required to log in.

`v1.34.0`

Compare Source

Add buf config ls-modules command to list configured modules.
Fix issue where buf generate would succeed on missing insertion points and panic on empty insertion point files.
Update buf generate to allow the use of Editions syntax when doing local code generation by proxying to a protoc binary (for languages where code gen is implemented inside of protoc instead of in a plugin: Java, C++, Python, etc).
Allow use of an array of strings for the protoc_path property of for buf.gen.yaml, where the first array element is the actual path and other array elements are extra arguments that are passed to protoc each time it is invoked.

`v1.33.0`

Compare Source

Allow user to override --source-control-url and --create-default-label when using --git-metadata with buf push.
Fix buf push --git-metadata when local tags point to different objects than the remote tags.
Fix issue where comment ignores were not respected for PROTOVALIDATE lint rule violations.
Add buf beta registry label {create,get,list} to replace buf beta registry {draft, tag} commands.
Update buf beta commit {get,list} command outputs to display create time and stop displaying associated tags.
Change the behavior of buf beta commit list <buf.build/owner/repository> when the reference is empty. It now lists commits in the repository instead of listing commits of the default label.
Update output of buf format to canonicalize the punctuation used in message literals in option values. The output now always uses { and } instead of < and >; it adds : separators between field names and message values if the source omitted them, and it removes unnecessary separators between fields (, and ; are allowed, but neither is needed).
Update buf format -w so that it does not touch files whose contents don't actually change. This eliminates noisy notifications to file-system-watcher tools that are watching the directory that contains proto sources.
Update buf generate to work with plugins provided by protoc for versions v24.0 to v25.3. Editions support was experimental in these releases, and the plugins advertise incomplete support for editions, which triggers buf to report an error. With this fix, these plugins can be used again as long as none of the input files use editions syntax.
Add buf push --exclude-unnamed flag to exclude unnamed modules when pushing to the BSR.

`v1.32.2`

Compare Source

Update buf generate to warn instead of error when proto3 optional is required but not supported by a plugin.

`v1.32.1`

Compare Source

Fix archive and git inputs so that --path and --exclude-path paths are relative to the #subdir rather than the root of the input. This fixes an unintended behavior change that was introduced in v1.32.0.
Add module input for protoc-gen-buf-lint and protoc-gen-buf-breaking to allow users to specify the module for v2 configuration files.

`v1.32.0`

Compare Source

Add version v2 for buf.yaml and buf.gen.yaml configuration files.
Add buf config migrate to migrate configuration files to the latest version (now v2).
Move buf mod init to buf config init. buf mod init is now deprecated.
Move buf mod ls-lint-rules to buf config ls-lint-rules. buf mod ls-lint-rules is now deprecated.
Move buf mod ls-breaking-rules to buf config ls-breaking-rules. buf mod ls-breaking-rules is now deprecated.
Move buf mod prune to buf dep prune. buf mod prune is now deprecated.
Move buf mod update to buf dep update. buf mod update is now deprecated.
Move buf mod {clear-cache,cc} to buf registry cc. buf mod {clear-cache,cc} is now deprecated.
Move buf beta graph to stable as buf dep graph.
Change the default visibility of buf push --create-visibility to private when the --create flag is set. Users are no longer required to set --create-visibility when running buf push --create.
Add buf push --label, which allows users to set labels when pushing new commits to the BSR.
Add buf push --source-control-url, which allows users to associate commits pushed to the BSR with a URL to a source code repository.
Add buf push --create-default-label, which allows users to set a default label for a repository when calling buf push --create.
Add buf push --git-metadata, which automatically sets appropriate --label, --source-control-url, and --create-default-label flags based on the current Git repository.
Add buf convert --validate to apply protovalidate rules to incoming messages specified with --from.
Deprecate buf mod open.
Delete buf beta migrate-v1beta1 This is now replaced with buf config migrate.
Add buf registry sdk version to get the version of a Generated SDK for a module and plugin.
Add buf beta registry archive and buf beta registry unarchive commands for archiving and unarchiving labels on the BSR.
Add support for Protobuf Editions. This allows buf to be used with sources that use edition 2023, instead of proto2 or proto3 syntax. This also updates the protoc-gen-buf-breaking and protoc-gen-buf-lint Protobuf plugins to support files that use edition 2023.
Update buf breaking rules to work with Protobuf Editions. To support Editions, some rules have been deprecated and replaced with Editions-aware rules. All deprecated rules continue to work for existing users.
- FIELD_SAME_CTYPE has been replaced with FIELD_SAME_CPP_STRING_TYPE, which considers both ctype field options and new (pb.cpp).string_type features when deciding on backwards compatibility.
- FIELD_SAME_LABEL has been replaced with three rules that all check "cardinality". The new rules can distinguish between maps and other repeated fields and between implicit and explicit field presence. The new rules are:
  1. FIELD_SAME_CARDINALITY in the FILE and PACKAGE categories.
  2. FIELD_WIRE_COMPATIBLE_CARDINALITY in the WIRE category.
  3. FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY in the WIRE_JSON category.
- FILE_SAME_JAVA_STRING_CHECK_UTF8 has been replaced with FIELD_SAME_JAVA_UTF8_VALIDATION, which considers both the java_string_check_utf8 file option and (pb.java).utf8_validation features when deciding on backwards compatibility.
- Add to the existing FILE_SAME_SYNTAX rule with a few related rules that can catch the same sort of compatibility issues, but in an Editions source file that changes feature values:
  1. MESSAGE_SAME_JSON_FORMAT and ENUM_SAME_JSON_FORMAT catch changes to the json_format feature, 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.
  2. FIELD_SAME_UTF8_VALIDATION catches changes to the utf8_validation feature, which controls validation of string values.
  3. ENUM_SAME_TYPE catches changes to an enum's type, open vs. closed.
Add support for extensions to buf breaking. All existing rules for fields are now applied to extensions, except for FIELD_NO_DELETE (and its variants). There are also new EXTENSION_NO_DELETE and PACKAGE_EXTENSION_NO_DELETE rules for catching deletions of an extension. The new rules are not active by default in existing v1 and v1beta1 configurations, for backwards-compatibility reasons. Migrate your config to v2 to use them.
Add support for top-level extensions to buf lint. It previously only checked extensions that were defined inside of messages.
Add a new FIELD_NOT_REQUIRED lint rule that prevents use of required in proto2 files and of features.field_presence = LEGACY_REQUIRED in Editions files. This new rule is not active by default in existing v1 and v1beta1 configurations, for backwards-compatibility reasons. Migrate your config to v2 to use them.

`v1.31.0`

Compare Source

Update dependencies.

`v1.30.1`

Compare Source

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

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.

[ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Apr 20 '24 14:04 renovate[bot]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

37 additional dependencies were updated

Details:

Package	Change
`google.golang.org/protobuf`	`v1.34.2` -> `v1.34.3-0.20240816073751-94ecbc261689`
`buf.build/gen/go/bufbuild/protovalidate/protocolbuffers/go`	`v1.33.0-20240221180331-f05a6f4403ce.1` -> `v1.34.2-20240717164558-a6c49f84cc0f.2`
`github.com/Microsoft/go-winio`	`v0.6.1` -> `v0.6.2`
`github.com/antlr4-go/antlr/v4`	`v4.13.0` -> `v4.13.1`
`github.com/bufbuild/protocompile`	`v0.9.0` -> `v0.14.1`
`github.com/bufbuild/protovalidate-go`	`v0.6.0` -> `v0.6.5`
`github.com/bufbuild/protoyaml-go`	`v0.1.8` -> `v0.1.12`
`github.com/distribution/reference`	`v0.5.0` -> `v0.6.0`
`github.com/docker/cli`	`v25.0.4+incompatible` -> `v27.2.1+incompatible`
`github.com/docker/docker`	`v25.0.6+incompatible` -> `v27.2.1+incompatible`
`github.com/docker/docker-credential-helpers`	`v0.8.1` -> `v0.8.2`
`github.com/felixge/fgprof`	`v0.9.4` -> `v0.9.5`
`github.com/go-chi/chi/v5`	`v5.0.12` -> `v5.1.0`
`github.com/gofrs/uuid/v5`	`v5.0.0` -> `v5.3.0`
`github.com/google/cel-go`	`v0.20.1` -> `v0.21.0`
`github.com/google/go-containerregistry`	`v0.19.0` -> `v0.20.2`
`github.com/google/pprof`	`v0.0.0-20240422182052-72c8669ad3e7` -> `v0.0.0-20240910150728-a0b0bb1d4134`
`github.com/klauspost/compress`	`v1.17.7` -> `v1.17.9`
`github.com/prometheus/client_model`	`v0.5.0` -> `v0.6.1`
`github.com/rs/cors`	`v1.11.0` -> `v1.11.1`
`github.com/spf13/cobra`	`v1.8.0` -> `v1.8.1`
`go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp`	`v0.49.0` -> `v0.54.0`
`go.opentelemetry.io/otel`	`v1.24.0` -> `v1.30.0`
`go.opentelemetry.io/otel/metric`	`v1.24.0` -> `v1.30.0`
`go.opentelemetry.io/otel/sdk`	`v1.24.0` -> `v1.30.0`
`go.opentelemetry.io/otel/trace`	`v1.24.0` -> `v1.30.0`
`golang.org/x/crypto`	`v0.24.0` -> `v0.27.0`
`golang.org/x/exp`	`v0.0.0-20240416160154-fe59bbe5cc7f` -> `v0.0.0-20240909161429-701f63a606c0`
`golang.org/x/mod`	`v0.17.0` -> `v0.21.0`
`golang.org/x/net`	`v0.26.0` -> `v0.29.0`
`golang.org/x/sync`	`v0.7.0` -> `v0.8.0`
`golang.org/x/sys`	`v0.21.0` -> `v0.25.0`
`golang.org/x/term`	`v0.21.0` -> `v0.24.0`
`golang.org/x/text`	`v0.16.0` -> `v0.18.0`
`golang.org/x/tools`	`v0.21.1-0.20240508182429-e35e4ccd0d2d` -> `v0.25.0`
`google.golang.org/genproto/googleapis/api`	`v0.0.0-20240604185151-ef581f913117` -> `v0.0.0-20240903143218-8af14fe29dc1`
`google.golang.org/genproto/googleapis/rpc`	`v0.0.0-20240604185151-ef581f913117` -> `v0.0.0-20240903143218-8af14fe29dc1`

Jun 13 '24 17:06 renovate[bot]