build(deps): bump errorprone from 2.30.0 to 2.32.0

[dependabot]

Bumps errorprone from 2.30.0 to 2.32.0.
Updates com.google.errorprone:error_prone_core from 2.30.0 to 2.32.0

Release notes

Sourced from com.google.errorprone:error_prone_core's releases.

Error Prone 2.32.0

The minimum support JDK version to run Error Prone is now JDK 17 (#3803).

Using Error Prone to compile code that is deployed to earlier versions is still fully supported, but will requires using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Full changelog: google/error-prone@v2.31.0...v2.32.0

Error Prone 2.31.0

This is the last planned minor release of Error Prone that will support running on JDK 11, see #3803. Using Error Prone to compile code that is deployed to earlier versions will continue to be fully supported, but will require using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Changes:

• Introduce @ThreadSafeTypeParameter with enforcement by ThreadSafe
• Improved support for latest JDK 24 EA builds
• Error Prone is now distributed as a Multi-Release jar (#3756)

New checks:

• AutoValueBoxedValues: AutoValue instances should not usually contain boxed types that are not Nullable. We recommend removing the unnecessary boxing.

Full changelog: google/error-prone@v2.30.0...v2.31.0

Commits

• 0fe0961 Release Error Prone 2.32.0
• 655bdc4 Update release.yml: remove JDK 11
• a9ff9b1 Update ci.yml: remove JDK 11
• 4e0b19c Start using Java > 11 language features in Error Prone tests
• 4b5ee1e Update ci.yml: always set up JDK 17
• 494e2c6 Don't perform the inlining if parameter names are stripped.
• dab4089 Add the name of the method to the diagnostic message for MemberName.
• 671ac41 Update ci.yml to use javadoc:javadoc
• 5bf91fb Replace {@link ThreadSafeTypeParameter} with {@code ThreadSafeTypeParameter}
• a5a7189 Replace ComparisonChain with a Comparator chain.
• Additional commits viewable in compare view

Updates com.google.errorprone:error_prone_annotations from 2.30.0 to 2.32.0

Release notes

Sourced from com.google.errorprone:error_prone_annotations's releases.

Error Prone 2.32.0

The minimum support JDK version to run Error Prone is now JDK 17 (#3803).

Using Error Prone to compile code that is deployed to earlier versions is still fully supported, but will requires using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Full changelog: google/error-prone@v2.31.0...v2.32.0

Error Prone 2.31.0

This is the last planned minor release of Error Prone that will support running on JDK 11, see #3803. Using Error Prone to compile code that is deployed to earlier versions will continue to be fully supported, but will require using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Changes:

• Introduce @ThreadSafeTypeParameter with enforcement by ThreadSafe
• Improved support for latest JDK 24 EA builds
• Error Prone is now distributed as a Multi-Release jar (#3756)

New checks:

• AutoValueBoxedValues: AutoValue instances should not usually contain boxed types that are not Nullable. We recommend removing the unnecessary boxing.

Full changelog: google/error-prone@v2.30.0...v2.31.0

Commits

• 0fe0961 Release Error Prone 2.32.0
• 655bdc4 Update release.yml: remove JDK 11
• a9ff9b1 Update ci.yml: remove JDK 11
• 4e0b19c Start using Java > 11 language features in Error Prone tests
• 4b5ee1e Update ci.yml: always set up JDK 17
• 494e2c6 Don't perform the inlining if parameter names are stripped.
• dab4089 Add the name of the method to the diagnostic message for MemberName.
• 671ac41 Update ci.yml to use javadoc:javadoc
• 5bf91fb Replace {@link ThreadSafeTypeParameter} with {@code ThreadSafeTypeParameter}
• a5a7189 Replace ComparisonChain with a Comparator chain.
• 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)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign lburgazzoli for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.