chore(deps-dev): bump @bufbuild/buf from 1.26.1 to 1.31.0 in /console

[dependabot]

Bumps @bufbuild/buf from 1.26.1 to 1.31.0.

Release notes

Sourced from @​bufbuild/buf's releases.

v1.31.0

• Update dependencies.

v1.30.1

• Fix issue where buf lint incorrectly reports an error for (buf.validate.field).repeated is set for a repeated validation rule.

v1.30.0

• Update buf generate so it populates the recently-added source_file_descriptors field of the CodeGeneratorRequest message. This provides the plugin with access to options that are configured to only be retained in source and not at runtime (via field option). Descriptors in the proto_file field will not include any options configured this way for the files named in file_to_generate field.
• Add --exclude-source-retention-options flag to buf build, which causes options configured to only be retained in source to be stripped from the output descriptors.

v1.29.0

• Add support for yaml format. All commands that take image inputs, output images, or convert between message formats, now take yaml as a format, in addition to the existing binpb and txtpb formats. Some examples:
  • buf build -o image.yaml
  • buf ls-files image.yaml
  • buf convert --type foo.Bar --from input.binpb --to output.yaml
• The yaml and json formats now accept two new options: use_proto_names and use_enum_numbers. This affects output serialization. Some examples:
  • buf convert --type foo.Bar --from input.binpb --to output.yaml#use_proto_names=true
  • buf convert --type foo.Bar --from input.binpb --to -#format=yaml,use_enum_numbers=true
• Fix issue where buf format would inadvertently mangle files that used the expanded Any syntax in option values.

v1.28.1

• The buf curl command has been updated to support the use of multiple schemas. This allows users to specify multiple --schema flags and/or to use both --schema and --reflect flags at the same time. The result is that additional sources can be consulted to resolve an element. This can be useful when the result of an RPC contains extensions or values in google.protobuf.Any messages that are not defined in the same schema that defines the RPC service.
• Fix issue where buf lint incorrectly reports error when (buf.validate.field).required is set for an optional field in proto3.

v1.28.0

• Add lint rules for protovalidate. buf lint will now verify that your protovalidate rules are valid. A single rule PROTOVALIDATE has been added to the DEFAULT group - given that protovalidate is net new, this does not represent a breaking change.
• Update buf beta price with the latest pricing information.
• Display a warning when reading a buf.lock with dependencies with b1 or b3 digests. b1 and b3 digests will be deprecated in a future version. Run buf mod update to update dependency digests.

v1.27.2

• Fix issue where buf build and other commands may fail when handling certain archives created on macOS that contain files with extended attributes.

v1.27.1

• Fix issue in v1.27.0 where --path did not work with workspaces under certain scenarios.

v1.27.0

• Fix issue where buf generate --exclude-path was not properly excluding paths for remote modules.
• Fix issue where buf curl had a user agent that did not properly place the extension as a suffix.
• Update buf beta price with the latest pricing information.

Changelog

Sourced from @​bufbuild/buf's changelog.

[v1.31.0] - 2024-04-23

• Update dependencies.

[v1.30.1] - 2024-04-03

• Fix issue where buf lint incorrectly reports an error for (buf.validate.field).repeated is set for a repeated validation rule.

[v1.30.0] - 2024-03-07

• Update buf generate so it populates the recently-added source_file_descriptors field of the CodeGeneratorRequest message. This provides the plugin with access to options that are configured to only be retained in source and not at runtime (via field option). Descriptors in the proto_file field will not include any options configured this way for the files named in file_to_generate field.
• Add --exclude-source-retention-options flag to buf build, which causes options configured to only be retained in source to be stripped from the output descriptors.

[v1.29.0] - 2024-01-24

• Add support for yaml format. All commands that take image inputs, output images, or convert between message formats, now take yaml as a format, in addition to the existing binpb and txtpb formats. Some examples:
  • buf build -o image.yaml
  • buf ls-files image.yaml
  • buf convert --type foo.Bar --from input.binpb --to output.yaml
• The yaml and json formats now accept two new options: use_proto_names and use_enum_numbers. This affects output serialization. Some examples:
  • buf convert --type foo.Bar --from input.binpb --to output.yaml#use_proto_names=true
  • buf convert --type foo.Bar --from input.binpb --to -#format=yaml,use_enum_numbers=true
• Fix issue where buf format would inadvertently mangle files that used the expanded Any syntax in option values.

[v1.28.1] - 2023-11-15

• The buf curl command has been updated to support the use of multiple schemas. This allows users to specify multiple --schema flags and/or to use both --schema and --reflect flags at the same time. The result is that additional sources can be consulted to resolve an element. This can be useful when the result of an RPC contains extensions or values in google.protobuf.Any messages that are not defined in the same schema that defines the RPC service.
• Fix issue where buf lint incorrectly reports error when (buf.validate.field).required is set for an optional field in proto3.

[v1.28.0] - 2023-11-10

... (truncated)

Commits

• c9863a6 Release v1.31.0 (#2908)
• 00dfa3d Bump connectrpc.com/connect from 1.16.0 to 1.16.1 (#2904)
• 5370d4a Make upgrade (#2905)
• 1607d07 Update user_id to reserved in UserPluginPreferences (#2898)
• 0b24de2 Make upgrade (#2892)
• a52805a Make upgrade (#2880)
• e9aaa1b Bump bufbuild/buf-setup-action from 1.30.0 to 1.30.1 (#2878)
• 5a71edd Return to development (#2866)
• a3f5940 Release v1.30.1 (#2865)
• aeb84da Update CHANGELOG.md for v1.30.1 (#2864)
• 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 29, 2024 3:37am

[dependabot]

Superseded by #7985.