build(deps): Bump github.com/bufbuild/buf from 1.9.0 to 1.46.0

[dependabot]

Bumps github.com/bufbuild/buf from 1.9.0 to 1.46.0.

Release notes

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

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.

v1.38.0

• Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
• Fix issue with directory inputs for v2 workspaces where the specified directory was not itself a path to a module, but contained directories with modules, and the modules would not build.
• Stop creating empty buf.lock files when buf dep update does not find new dependencies to update and there is no existing buf.lock.
• Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the same directory as buf.yaml if a module does not have a license file or doc file in the module's directory.
• Fix constraints of --path flag for lint and breaking rules to avoid resolving all files

... (truncated)

Changelog

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

[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

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

• 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] - 2024-09-04

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

... (truncated)

Commits

• 72a73ea Release v1.46.0 (#3432)
• f9856b2 Add audit logging resource and events for check plugin (#3430)
• ed28039 Add buf registry whoami command (#3416)
• b5f41e3 Fix LSP leading comment formatting (#3424)
• 225aeaf Split bufapi module to separate packages (#3428)
• 91bf561 Bump github.com/quic-go/quic-go from 0.48.0 to 0.48.1 (#3422)
• 40e649d Update issue templates (#3427)
• 9ec7745 Add deprecated field to curated plugins config and upload (#3421)
• 866295e Update go registry protos (#3420)
• d5bf43c Update bufplugin dependency (#3419)
• 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, S:automerge.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.