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

[dependabot]

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

Release notes

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

v1.35.1

• 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

• 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

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

... (truncated)

Changelog

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

[v1.35.1] - 2024-07-24

• 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] - 2024-07-22

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

... (truncated)

Commits

• f37053e Release v1.35.1 (#3186)
• 9b236ca Only check directories in workspace targeting fallback logic (#3184)
• 8be3d05 Validate domain in buf registry login and logout (#3182)
• 8c22e90 Fix git ref to allow branches and tags (#3095)
• eee05d1 Return to development (#3179)
• da90244 Release v1.35.0 (#3178)
• 0b436b4 Add comments to addFuncs (#3172)
• 8996858 Add OAuth2 client to support device flow (#3143)
• 0d9adad Export target framework conversion functions (#3164)
• afb50e1 Add new cmake registry type (#3156)
• 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.

[dependabot]

Superseded by #191.