search

edgelesssys / constellation

Constellation is the first Confidential Kubernetes. Constellation shields entire Kubernetes clusters from the (cloud) infrastructure using confidential computing.
GNU Affero General Public License v3.0
903 stars 47 forks source link

deps: update bufbuild/buf to v1.34.0 #3210

Open renovate[bot] opened 1 week ago

renovate[bot] commented 1 week ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
com_github_bufbuild_buf_darwin_amd64 http_archive minor v1.31.0 -> v1.34.0
com_github_bufbuild_buf_darwin_arm64 http_archive minor v1.31.0 -> v1.34.0
com_github_bufbuild_buf_linux_amd64 http_archive minor v1.31.0 -> v1.34.0
com_github_bufbuild_buf_linux_arm64 http_archive minor v1.31.0 -> v1.34.0

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

bufbuild/buf (com_github_bufbuild_buf_darwin_amd64) ### [`v1.34.0`](https://togithub.com/bufbuild/buf/blob/HEAD/CHANGELOG.md#v1340---2024-06-21) [Compare Source](https://togithub.com/bufbuild/buf/compare/v1.33.0...v1.34.0) - 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`](https://togithub.com/bufbuild/buf/blob/HEAD/CHANGELOG.md#v1330---2024-06-13) [Compare Source](https://togithub.com/bufbuild/buf/compare/v1.32.2...v1.33.0) - 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 ` 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`](https://togithub.com/bufbuild/buf/blob/HEAD/CHANGELOG.md#v1322---2024-05-28) [Compare Source](https://togithub.com/bufbuild/buf/compare/v1.32.1...v1.32.2) - Update `buf generate` to warn instead of error when proto3 optional is required but not supported by a plugin. ### [`v1.32.1`](https://togithub.com/bufbuild/buf/blob/HEAD/CHANGELOG.md#v1321---2024-05-21) [Compare Source](https://togithub.com/bufbuild/buf/compare/v1.32.0...v1.32.1) - 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`](https://togithub.com/bufbuild/buf/blob/HEAD/CHANGELOG.md#v1320---2024-05-16) [Compare Source](https://togithub.com/bufbuild/buf/compare/v1.31.0...v1.32.0) - 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](https://togithub.com/bufbuild/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.

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 these updates again.

This PR has been generated by Mend Renovate. View repository job log here.

netlify[bot] commented 1 week ago

Deploy Preview for constellation-docs canceled.

Name Link
Latest commit 43af3d7d30553ad2721953bd03676388e4e4d232
Latest deploy log https://app.netlify.com/sites/constellation-docs/deploys/667d27a09bec590008470751
renovate[bot] commented 1 week ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.