build(deps): Bump github.com/bufbuild/buf from 1.35.1 to 1.47.2

[dependabot]

Bumps github.com/bufbuild/buf from 1.35.1 to 1.47.2.

Release notes

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

v1.47.2

• Update the patch version to resolve NPM packaging issues. No command updates or user changes.

v1.47.1

• Update the patch version to resolve NPM packaging issues. No command updates or user changes.

v1.47.0

• Move buf registry commit to buf registry module commit. Command buf registry commit is now deprecated.
• Move buf registry label to buf registry module label. Command buf registry label is now deprecated.

v1.46.0

• Add buf registry whoami command, which checks if you are logged in to the Buf Schema Registry at a given domain.

v1.45.0

• Update buf registry module info --format=json to add default_label_name, which provides the name of the default label of a module.

v1.44.0

• Update the PROTOVALIDATE lint rule to check example field options. Examples will be checked that they satisfy the field constraints, and are only present if constraints are present.
• Update the PROTOVALIDATE lint rule to check predefined rules. Predefined rules will be checked that they compile.
• Add support for a WebAssembly (Wasm) runtime for custom lint and breaking changes plugins. Use the .wasm file extension to specify a path to a Wasm plugin.

v1.43.0

• Add new experimental LSP support under buf beta lsp.

v1.42.0

• Add support for custom lint and breaking change plugins. See our launch blog post for more details!
• Add buf dep graph --format flag that defaults to dot, and adds the option json, to print the dependency graph in JSON format.
• Fix bugs in buf format where trailing comments on commas in message literals were not properly propagated 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.0

• Add HTTP/3 support for gRPC with buf curl.
• Fix issue where errors from protoc plugins may be overwritten when executing plugins in parallel.

v1.40.1

• Fix issue with buf lint where comment ignores in the shape of // buf:lint:ignore <RULE_ID> <extra comment> were not recognized due to the extra comment.

v1.40.0

• Add concept of a default lint or breaking rule, which is printed out as a property when running buf config ls-{breaking,lint}-rules. Default rules are those rules which are run if no lint or breaking rules are explicitly configured in your buf.yaml.
• Rename DEFAULT lint rule category to STANDARD. With the concept of default rules being introduced, having a category named DEFAULT is confusing, as while it happens that all the rules in the DEFAULT lint category are also default rules, the name has become overloaded. As with all buf changes, this change is backwards-compatible: the DEFAULT lint category continues to work, and always will. We recommend changing to STANDARD, however.

v1.39.0

• Fix git input handling of relative HEAD refs without branch names.
• Add includes key to module configurations in v2 buf.yaml, accepting a list of directories.
  • If includes is specified, a proto file is considered in the module only if it is in one of the directories specified.
  • If both includes and excludes keys are specified for a module, a proto file is considered part of this module if it is contained in any of the include paths and not in any of the exclude paths.
• Allow multiple module configurations in the same v2 buf.yaml to have the same directory path.

... (truncated)

Changelog

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

[v1.47.2] - 2024-11-14

• Update the patch version to resolve NPM packaging issues. No command updates or user changes.

[v1.47.1] - 2024-11-14

• Update the patch version to resolve NPM packaging issues. No command updates or user changes.

[v1.47.0] - 2024-11-13

• Move buf registry commit to buf registry module commit. Command buf registry commit is now deprecated.
• Move buf registry label to buf registry module label. Command buf registry label is now deprecated.

[v1.46.0] - 2024-10-29

• Add buf registry whoami command, which checks if you are logged in to the Buf Schema Registry at a given domain.

[v1.45.0] - 2024-10-08

• Update buf registry module info --format=json to add default_label_name, which provides the name of the default label of a module.

[v1.44.0] - 2024-10-03

• Update the PROTOVALIDATE lint rule to check example field options. Examples will be checked that they satisfy the field constraints, and are only present if constraints are present.
• Update the PROTOVALIDATE lint rule to check predefined rules. Predefined rules will be checked that they compile.
• Add support for a WebAssembly (Wasm) runtime for custom lint and breaking changes plugins. Use the .wasm file extension to specify a path to a Wasm plugin.

[v1.43.0] - 2024-09-30

• Add new experimental LSP support under buf beta lsp.

[v1.42.0] - 2024-09-18

• Add support for custom lint and breaking change plugins. See our launch blog post for more details!
• Add buf dep graph --format flag that defaults to dot, and adds the option json, to print the dependency graph in JSON format.
• Fix bugs in buf format where trailing comments on commas in message literals were not properly propagated 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.0] - 2024-09-11

... (truncated)

Commits

• 13828a3 Release v1.47.2 (#3472)
• be349d1 Return to development (#3471)
• 8688d16 Release v1.47.1 (#3470)
• d12a559 Return to development (#3467)
• 3f619b8 Release v1.47.0 (#3466)
• 5fda66b Move registry commit and label commands under modules (#3454)
• 10ddcf5 Add bufplugin package (#3431)
• dae748f Make upgrade (#3463)
• 4343d43 Do not format a file that contains an error in the LSP (#3447)
• 62082b2 Adjust cache ModuleDataProvider to re-retrieve delegate values from store a...
• 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)

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

---

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.