Bump build.buf:buf from 1.31.0 to 1.32.0 (#133)

Bumps [build.buf:buf](https://github.com/bufbuild/buf) from 1.31.0 to
1.32.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/bufbuild/buf/releases">build.buf:buf's
releases</a>.</em></p>
<blockquote>
<h2>v1.32.0</h2>
<p>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
<code>v1.32.0</code> release of buf introduces <code>v2</code> config
formats for both <code>buf.yaml</code> and <code>buf.gen.yaml</code>.
All your current commands and <code>v1</code> configuration continue to
work, so you can upgrade to <code>v2</code> configuration when
appropriate.</p>
<p>To read more about what's new, check out our blog and our docs:</p>
<ul>
<li><a href="https://buf.build/blog/buf-cli-next-generation">Introducing
the next generation of the Buf CLI: still v1 and
backwards-compatible</a></li>
<li><a
href="https://buf.build/blog/enhanced-buf-push-bsr-ui">Introducing the
newly improved BSR UI and buf push experience</a></li>
<li><a
href="https://buf.build/docs/migration-guides/migrate-v2-config-files">Migrate
to v2 configuration files</a></li>
</ul>
<hr />
<ul>
<li>Add version <code>v2</code> for <code>buf.yaml</code> and
<code>buf.gen.yaml</code> configuration files.</li>
<li>Add <code>buf config migrate</code> to migrate configuration files
to the latest version (now <code>v2</code>).</li>
<li>Move <code>buf mod init</code> to <code>buf config init</code>.
<code>buf mod init</code> is now deprecated.</li>
<li>Move <code>buf mod ls-lint-rules</code> to <code>buf config
ls-lint-rules</code>. <code>buf mod ls-lint-rules</code> is now
deprecated.</li>
<li>Move <code>buf mod ls-breaking-rules</code> to <code>buf config
ls-breaking-rules</code>. <code>buf mod ls-breaking-rules</code> is now
deprecated.</li>
<li>Move <code>buf mod prune</code> to <code>buf dep prune</code>.
<code>buf mod prune</code> is now deprecated.</li>
<li>Move <code>buf mod update</code> to <code>buf dep update</code>.
<code>buf mod update</code> is now deprecated.</li>
<li>Move <code>buf mod {clear-cache,cc}</code> to <code>buf registry
cc</code>. <code>buf mod {clear-cache,cc}</code> is now deprecated.</li>
<li>Move <code>buf beta graph</code> to stable as <code>buf dep
graph</code>.</li>
<li>Change the default visibility of <code>buf push
--create-visibility</code> to <code>private</code> when the
<code>--create</code> flag is set. Users are no longer required to set
<code>--create-visibility</code> when running <code>buf push
--create</code>.</li>
<li>Add <code>buf push --label</code>, which allows users to set labels
when pushing new commits to the BSR.</li>
<li>Add <code>buf push --source-control-url</code>, which allows users
to associate commits pushed to the BSR with a URL to a source code
repository.</li>
<li>Add <code>buf push --create-default-label</code>, which allows users
to set a default label for a repository when calling <code>buf push
--create</code>.</li>
<li>Add <code>buf push --git-metadata</code>, which automatically sets
appropriate <code>--label</code>, <code>--source-control-url</code>, and
<code>--create-default-label</code> flags based on the current Git
repository.</li>
<li>Add <code>buf convert --validate</code> to apply <a
href="https://github.com/bufbuild/protovalidate">protovalidate</a> rules
to incoming messages specified with <code>--from</code>.</li>
<li>Deprecate <code>buf mod open</code>.</li>
<li>Delete <code>buf beta migrate-v1beta1</code> This is now replaced
with <code>buf config migrate</code>.</li>
<li>Add <code>buf registry sdk version</code> to get the version of a
Generated SDK for a module and plugin.</li>
<li>Add <code>buf beta registry archive</code> and <code>buf beta
registry unarchive</code> commands for archiving and unarchiving labels
on the BSR.</li>
<li>Add support for Protobuf Editions. This allows <code>buf</code> to
be used with sources that use edition 2023, instead of proto2 or proto3
syntax. This also updates the <code>protoc-gen-buf-breaking</code> and
<code>protoc-gen-buf-lint</code> Protobuf plugins to support files that
use edition 2023.</li>
<li>Update <code>buf breaking</code> rules to work with Protobuf
Editions. To support Editions, some rules have been deprecated and
replaced with Editions-aware rules. All deprecated rules continue to
work for existing users.
<ul>
<li><code>FIELD_SAME_CTYPE</code> has been replaced with
<code>FIELD_SAME_CPP_STRING_TYPE</code>, which considers both
<code>ctype</code> field options and new
<code>(pb.cpp).string_type</code> features when deciding on backwards
compatibility.</li>
<li><code>FIELD_SAME_LABEL</code> has been replaced with three rules
that all check &quot;cardinality&quot;. The new rules can distinguish
between maps and other repeated fields and between implicit and explicit
field presence. The new rules are:
<ol>
<li><code>FIELD_SAME_CARDINALITY</code> in the <code>FILE</code> and
<code>PACKAGE</code> categories.</li>
<li><code>FIELD_WIRE_COMPATIBLE_CARDINALITY</code> in the
<code>WIRE</code> category.</li>
<li><code>FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY</code> in the
<code>WIRE_JSON</code> category.</li>
</ol>
</li>
<li><code>FILE_SAME_JAVA_STRING_CHECK_UTF8</code> has been replaced with
<code>FIELD_SAME_JAVA_UTF8_VALIDATION</code>, which considers both the
<code>java_string_check_utf8</code> file option and
<code>(pb.java).utf8_validation</code> features when deciding on
backwards compatibility.</li>
<li>Add to the existing <code>FILE_SAME_SYNTAX</code> rule with a few
related rules that can catch the same sort of compatibility issues, but
in an Editions source file that changes feature values:
<ol>
<li><code>MESSAGE_SAME_JSON_FORMAT</code> and
<code>ENUM_SAME_JSON_FORMAT</code> catch changes to the
<code>json_format</code> feature, which controls whether support for the
JSON format is best-effort or properly supported. When supported, the
compiler performs more checks relating to field name collisions for the
JSON format as well as for FieldMask usage.</li>
<li><code>FIELD_SAME_UTF8_VALIDATION</code> catches changes to the
<code>utf8_validation</code> feature, which controls validation of
string values.</li>
<li><code>ENUM_SAME_TYPE</code> catches changes to an enum's type, open
vs. closed.</li>
</ol>
</li>
</ul>
</li>
<li>Add support for extensions to <code>buf breaking</code>. All
existing rules for fields are now applied to extensions, except for
<code>FIELD_NO_DELETE</code> (and its variants). There are also new
<code>EXTENSION_NO_DELETE</code> and
<code>PACKAGE_EXTENSION_NO_DELETE</code> rules for catching deletions of
an extension. The new rules are not active by default in existing
<code>v1</code> and <code>v1beta1</code> configurations, for
backwards-compatibility reasons. Migrate your config to <code>v2</code>
to use them.</li>
<li>Add support for top-level extensions to <code>buf lint</code>. It
previously only checked extensions that were defined inside of
messages.</li>
<li>Add a new <code>FIELD_NOT_REQUIRED</code> lint rule that prevents
use of required in proto2 files and of <code>features.field_presence =
LEGACY_REQUIRED</code> in Editions files. This new rule is not active by
default in existing <code>v1</code> and <code>v1beta1</code>
configurations, for backwards-compatibility reasons. Migrate your config
to <code>v2</code> to use them.</li>
</ul>
<h2>v1.32.0-beta.1</h2>
<p>This is the first beta release of the next generation of the Buf CLI.
This beta release is being used by some of our customers to ensure we've
kept compatibility, and to try some of its new features. Don't worry -
the next generation of the <code>buf</code> CLI continues to be
<code>v1</code>, and is completely backwards-compatible - all of your
workflows will continue to work. Buf is enterprise-grade software, and
we want you to be minimally impacted.</p>
<p>There's some exciting improvements coming in the next generation of
the <code>buf</code> CLI, and we look forward to sharing it more widely
in the coming weeks. If you'd like to be part of the private beta, <a
href="https://github.com/bufbuild/buf/blob/HEAD/mailto:[email protected]">email
us</a> with the subject line &quot;Beta&quot; and we'll be happy to talk
- we'll add more users as we have capacity. While you are free to give
this beta release a spin without being added to our private beta, we
wouldn't recommend using it outside of our private beta just yet!</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/bufbuild/buf/blob/main/CHANGELOG.md">build.buf:buf's
changelog</a>.</em></p>
<blockquote>
<h2>[v1.32.0] - 2024-05-16</h2>
<ul>
<li>Add version <code>v2</code> for <code>buf.yaml</code> and
<code>buf.gen.yaml</code> configuration files.</li>
<li>Add <code>buf config migrate</code> to migrate configuration files
to the latest version (now <code>v2</code>).</li>
<li>Move <code>buf mod init</code> to <code>buf config init</code>.
<code>buf mod init</code> is now deprecated.</li>
<li>Move <code>buf mod ls-lint-rules</code> to <code>buf config
ls-lint-rules</code>. <code>buf mod ls-lint-rules</code> is now
deprecated.</li>
<li>Move <code>buf mod ls-breaking-rules</code> to <code>buf config
ls-breaking-rules</code>. <code>buf mod ls-breaking-rules</code>
is now deprecated.</li>
<li>Move <code>buf mod prune</code> to <code>buf dep prune</code>.
<code>buf mod prune</code> is now deprecated.</li>
<li>Move <code>buf mod update</code> to <code>buf dep update</code>.
<code>buf mod update</code> is now deprecated.</li>
<li>Move <code>buf mod {clear-cache,cc}</code> to <code>buf registry
cc</code>. <code>buf mod {clear-cache,cc}</code> is now
deprecated.</li>
<li>Move <code>buf beta graph</code> to stable as <code>buf dep
graph</code>.</li>
<li>Change the default visibility of <code>buf push
--create-visibility</code> to <code>private</code> when the
<code>--create</code>
flag is set. Users are no longer required to set
<code>--create-visibility</code> when running
<code>buf push --create</code>.</li>
<li>Add <code>buf push --label</code>, which allows users to set labels
when pushing new commits to the BSR.</li>
<li>Add <code>buf push --source-control-url</code>, which allows users
to associate commits pushed to the BSR
with a URL to a source code repository.</li>
<li>Add <code>buf push --create-default-label</code>, which allows users
to set a default label for a repository
when calling <code>buf push --create</code>.</li>
<li>Add <code>buf push --git-metadata</code>, which automatically sets
appropriate <code>--label</code>,
<code>--source-control-url</code>, and
<code>--create-default-label</code> flags based on the current Git
repository.</li>
<li>Add <code>buf convert --validate</code> to apply <a
href="https://github.com/bufbuild/protovalidate">protovalidate</a>
rules to incoming messages specified with <code>--from</code>.</li>
<li>Deprecate <code>buf mod open</code>.</li>
<li>Delete <code>buf beta migrate-v1beta1</code> This is now replaced
with <code>buf config migrate</code>.</li>
<li>Add <code>buf registry sdk version</code> to get the version of a
Generated SDK for a module and plugin.</li>
<li>Add <code>buf beta registry archive</code> and <code>buf beta
registry unarchive</code> commands for archiving and
unarchiving labels on the BSR.</li>
<li>Add support for Protobuf Editions. This allows <code>buf</code> to
be used with sources that use edition
2023, instead of proto2 or proto3 syntax. This also updates the
<code>protoc-gen-buf-breaking</code> and
<code>protoc-gen-buf-lint</code> Protobuf plugins to support files that
use edition 2023.</li>
<li>Update <code>buf breaking</code> rules to work with Protobuf
Editions. To support Editions, some rules have
been deprecated and replaced with Editions-aware rules. All deprecated
rules continue to work
for existing users.
<ul>
<li><code>FIELD_SAME_CTYPE</code> has been replaced with
<code>FIELD_SAME_CPP_STRING_TYPE</code>, which considers both
<code>ctype</code> field options and new
<code>(pb.cpp).string_type</code> features when deciding on backwards
compatibility.</li>
<li><code>FIELD_SAME_LABEL</code> has been replaced with three rules
that all check &quot;cardinality&quot;. The new
rules can distinguish between maps and other repeated fields and between
implicit and explicit
field presence. The new rules are:
<ol>
<li><code>FIELD_SAME_CARDINALITY</code> in the <code>FILE</code> and
<code>PACKAGE</code> categories.</li>
<li><code>FIELD_WIRE_COMPATIBLE_CARDINALITY</code> in the
<code>WIRE</code> category.</li>
<li><code>FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY</code> in the
<code>WIRE_JSON</code> category.</li>
</ol>
</li>
<li><code>FILE_SAME_JAVA_STRING_CHECK_UTF8</code> has been replaced with
<code>FIELD_SAME_JAVA_UTF8_VALIDATION</code>,
which considers both the <code>java_string_check_utf8</code> file option
and <code>(pb.java).utf8_validation</code>
features when deciding on backwards compatibility.</li>
<li>Add to the existing <code>FILE_SAME_SYNTAX</code> rule with a few
related rules that can catch the same</li>
</ul>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/bufbuild/buf/commit/c8b09954669528801fbee952f3fda165c50b601b"><code>c8b0995</code></a>
Release v1.32.0 (<a
href="https://redirect.github.com/bufbuild/buf/issues/2984">#2984</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/6004e2810e98d1c9fd6ceb78fb6fec1e4ff29567"><code>6004e28</code></a>
Add <code>--git-metadata</code> flag to <code>buf push</code> (<a
href="https://redirect.github.com/bufbuild/buf/issues/2953">#2953</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/d740a18f13090c9209edbb19292baea8880277b5"><code>d740a18</code></a>
Only archive and unarchive labels for target modules (<a
href="https://redirect.github.com/bufbuild/buf/issues/2983">#2983</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/bcf427c84ec04ac94a8af0f70a0ebdae97d56782"><code>bcf427c</code></a>
Change <code>buf beta registry label archive/unarchive</code> to `buf
beta registry arch...</li>
<li><a
href="https://github.com/bufbuild/buf/commit/4a0f6b41260c30d70b84870dc02da40ece9f1a50"><code>4a0f6b4</code></a>
Avoid pruning unused dependencies for <code>buf dep update</code> (<a
href="https://redirect.github.com/bufbuild/buf/issues/2966">#2966</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/06b7cf2f179c2b6f3a4b7207a024858049169a5c"><code>06b7cf2</code></a>
Merge and make upgrade</li>
<li><a
href="https://github.com/bufbuild/buf/commit/408c0439b067dbe1193f9ca5862432c1b9bdbd01"><code>408c043</code></a>
Cleanup CHANGELOG.md (<a
href="https://redirect.github.com/bufbuild/buf/issues/2979">#2979</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/6f133929048ff0532d2a6994807728f9ccb9a013"><code>6f13392</code></a>
Bump buf.build/gen/go/bufbuild/protovalidate/protocolbuffers/go from
1.33.0-2...</li>
<li><a
href="https://github.com/bufbuild/buf/commit/fc1ec890e040ec6a74bc47f1365d0bd3c1994e4d"><code>fc1ec89</code></a>
Tweak configuration of JSON format rules for buf breaking (<a
href="https://redirect.github.com/bufbuild/buf/issues/2978">#2978</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/fb0e9ac1001840ca8188745a4eb1347558997fc9"><code>fb0e9ac</code></a>
Update buf breaking checks to support extensions (<a
href="https://redirect.github.com/bufbuild/buf/issues/2960">#2960</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/bufbuild/buf/compare/v1.31.0...v1.32.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=build.buf:buf&package-manager=gradle&previous-version=1.31.0&new-version=1.32.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

gradle/libs.versions.toml

@@ -1,6 +1,6 @@
 [versions]
 assertj = "3.25.3"
-buf = "1.31.0"
+buf = "1.32.0"
 cel = "0.4.4"
 ipaddress = "5.5.0"
 junit = "5.10.2"