Bump github.com/bufbuild/buf from 1.30.0 to 1.34.0

[dependabot]

Bumps github.com/bufbuild/buf from 1.30.0 to 1.34.0.

Release notes

Sourced from github.com/bufbuild/buf's releases.

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

• 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

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

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

This release contains the (completely backwards-compatible) next generation of the Buf CLI. The Buf CLI and its associated configuration have been completely overhauled to support monorepos as first-class citizens. We'd call it a v2 of buf, but it's not. Buf is enterprise-grade software, and we want you to be minimally impacted. The v1.32.0 release of buf introduces v2 config formats for both buf.yaml and buf.gen.yaml. All your current commands and v1 configuration continue to work, so you can upgrade to v2 configuration when appropriate.

To read more about what's new, check out our blog and our docs:

• Introducing the next generation of the Buf CLI: still v1 and backwards-compatible
• Introducing the newly improved BSR UI and buf push experience
• Migrate to v2 configuration files

---

• 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.

... (truncated)

Changelog

Sourced from github.com/bufbuild/buf's changelog.

[v1.34.0] - 2024-06-21

• 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] - 2024-06-13

• 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] - 2024-05-28

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

[v1.32.1] - 2024-05-21

• 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

... (truncated)

Commits

• 3b5b535 Release v1.34.0 (#3104)
• 52a4214 Add buf config ls-modules (#3081)
• bbebe8a Set environment when running git commands (#3103)
• 28408f4 Improve error message for unauthenticated error (#3093)
• 0ad8677 Make upgrade (#3102)
• 45f8632 Allow protoc_path to be a slice so user can specify extra args (#3098)
• 0b7c7fa Improve insertion point behaviour (#3092)
• 6cdc860 Bump bufbuild/buf-setup-action from 1.32.2 to 1.33.0 (#3088)
• fc8e51c Fix other issue template (#3097)
• f634e4c Add reproduction comments to other template (#3096)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: T:dependencies.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.