Bump the maven group in /java with 4 updates

[dependabot]

Bumps the maven group in /java with 4 updates: com.google.guava:guava, com.google.protobuf:protobuf-java, io.grpc:grpc-protobuf and io.netty:netty-handler.

Updates com.google.guava:guava from 30.1.1-jre to 32.0.0-jre

Release notes

Sourced from com.google.guava:guava's releases.

32.0.0

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>32.0.0-jre</version>
  <!-- or, for Android: -->
  <version>32.0.0-android</version>
</dependency>

Jar files

• 32.0.0-jre.jar
• 32.0.0-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.1.jar

Javadoc

• 32.0.0-jre
• 32.0.0-android

JDiff

• 32.0.0-jre vs. 31.1-jre
• 32.0.0-android vs. 31.1-android
• 32.0.0-android vs. 32.0.0-jre

Changelog

Security fixes

• Reimplemented Files.createTempDir and FileBackedOutputStream to further address CVE-2020-8908 (#4011) and CVE-2023-2976 (#2575). (feb83a1c8f)

While CVE-2020-8908 was officially closed when we deprecated Files.createTempDir in Guava 30.0, we've heard from users that even recent versions of Guava have been listed as vulnerable in other databases of security vulnerabilities. In response, we've reimplemented the method (and the very rarely used FileBackedOutputStream class, which had a similar issue) to eliminate the insecure behavior entirely. This change could technically affect users in a number of different ways (discussed under "Incompatible changes" below), but in practice, the only problem users are likely to encounter is with Windows. If you are using those APIs under Windows, you should skip 32.0.0 and go straight to 32.0.1 which fixes the problem. (Unfortunately, we didn't think of the Windows problem until after the release. And while we warn that common.io in particular may not work under Windows, we didn't intend to regress support.) Sorry for the trouble.

Incompatible changes

Although this release bumps Guava's major version number, it makes no binary-incompatible changes to the guava artifact.

One change could cause issues for Widows users, and a few other changes could cause issues for users in more usual situations:

• The new implementations of Files.createTempDir and FileBackedOutputStream throw an exception under Windows. This is fixed in 32.0.1. Sorry for the trouble.
• guava-gwt now requires GWT 2.10.0.
• This release makes a binary-incompatible change to a @Beta API in the separate artifact guava-testlib. Specifically, we changed the return type of TestingExecutors.sameThreadScheduledExecutor to ListeningScheduledExecutorService. The old return type was a package-private class, which caused the Kotlin compiler to produce warnings. (dafaa3e435)

... (truncated)

Commits

• See full diff in compare view

Updates com.google.protobuf:protobuf-java from 3.19.4 to 3.25.5

Release notes

Sourced from com.google.protobuf:protobuf-java's releases.

Protocol Buffers v3.20.3

Java

• Refactoring java full runtime to reuse sub-message builders and prepare to migrate parsing logic from parse constructor to builder.
• Move proto wireformat parsing functionality from the private "parsing constructor" to the Builder class.
• Change the Lite runtime to prefer merging from the wireformat into mutable messages rather than building up a new immutable object before merging. This way results in fewer allocations and copy operations.
• Make message-type extensions merge from wire-format instead of building up instances and merging afterwards. This has much better performance.
• Fix TextFormat parser to build up recurring (but supposedly not repeated) sub-messages directly from text rather than building a new sub-message and merging the fully formed message into the existing field.
• This release addresses a Security Advisory for Java users

Protocol Buffers v3.20.2

C++

• Reduce memory consumption of MessageSet parsing
• This release addresses a Security Advisory for C++ and Python users

Protocol Buffers v3.20.1

PHP

• Fix building packaged PHP extension (#9727)
• Fixed composer.json to only advertise compatibility with PHP 7.0+. (#9819)

Ruby

• Disable the aarch64 build on macOS until it can be fixed. (#9816)

Other

• Fix versioning issues in 3.20.0

Protocol Buffers v3.20.1-rc1

PHP

• Fix building packaged PHP extension (#9727)

Other

• Fix versioning issues in 3.20.0

Protocol Buffers v3.20.0

2022-03-25 version 3.20.0 (C++/Java/Python/PHP/Objective-C/C#/Ruby/JavaScript)

Ruby

• Dropped Ruby 2.3 and 2.4 support for CI and releases. (#9311)
• Added Ruby 3.1 support for CI and releases (#9566).
• Message.decode/encode: Add recursion_limit option (#9218/#9486)
• Allocate with xrealloc()/xfree() so message allocation is visible to the Ruby GC. In certain tests this leads to much lower memory usage due to more frequent GC runs (#9586).
• Fix conversion of singleton classes in Ruby (#9342)

... (truncated)

Commits

• 9d0ec0f Updating version.json and repo version numbers to: 25.5
• 4a197e7 Merge pull request #18387 from protocolbuffers/cp-lp-25
• b5a7cf7 Remove RecursiveGroup test case which doesn't exist in 25.x pre-Editions
• f000b7e Fix merge conflict by adding optional label to proto2 unittest_lite.proto
• 4728531 Add recursion check when parsing unknown fields in Java.
• 850fcce Internal change
• b704498 Internal change
• e673479 Fix cord handling in DynamicMessage and oneofs. (#18375)
• 8a60b65 Merge pull request #17704 from protocolbuffers/cp-segv
• 94a2663 Fixed a SEGV when deep copying a non-reified sub-message.
• Additional commits viewable in compare view

Updates io.grpc:grpc-protobuf from 1.44.0 to 1.53.0

Release notes

Sourced from io.grpc:grpc-protobuf's releases.

v1.53.0

New Features

• googleapis: Allow user set c2p bootstrap config (#9856)
• xds: Add contain and stringMatcher in RouteConfiguration (#9845)
• core: Add grpc-previous-rpc-attempts to the initial response metadata (#9686)
• servlet: Implement gRPC server as a Servlet (#8596)
• authz: Implement static authorization server interceptor (#8934)

Examples

• servlet: Add servlet example (#8596)

Bug Fixes

• xds: Update xds error handling logic. Specifically:
  • When the ads stream is closed only send errors to subscribers that haven't yet gotten results
  • Timers to detect missing resources don’t start until the adsStream is ready (#9745)
  • Call subscriber onError callback when xds client fails to connect to server (#9827)
• core: Delay retriable stream master listener close until all sub streams are closed. This fixes the call executor lifecycle and prevents potential RejectedExecutionException. (#9754)
• core: Free unused MessageProducer in RetriableStream (#9853), fixing a Netty buffer memory leak for cancelled RPCs
• api: Fail with NullPointerException when a Metadata.Marshaller returns null bytes (#9781). This would previously cause a NullPointerException later during the RPC. Now the return value of the Marshaller is checked immediately, to help find the broken Marshaller

Behavior Changes

• xds: Disallow duplicate addresses in the RingHashLB. (#9776)
• xds: EDS weight sums are allowed up to max unsigned int (was max signed int) (#9765)
• xds: Drop xds v2 support (#9760)

Dependencies

• JUnit upgraded to 4.13.2
• bazel: Dropped support for Bazel 4. We track the two most recent major versions of Bazel, Bazel 5 and 6. Bazel 4 may still work, but we are no longer testing it
• bazel: Include Tomcat annotations dependency for @Generated as used by autovalue (#9762). Necessary for building xds and rls on Java 9+
• bazel: Export deps from Maven Central-specific stand-in targets (#9780). Some Maven Central artifacts are a combination of multiple Bazel targets, like grpc-core is composed of //core:inprocess, //core:internal, //core:util, //api. There is a “//core:core_maven” target used by maven_install that uses the other targets. Previously the target used runtime_deps to discourage their use by Bazel users, but that could cause compilation failures from lack of hjars. These targets now use exports

Acknowledgement

@​cpovirk @​niloc132 @​stephenh @​olderwei @​pandaapo @​panxuefeng

v1.52.1

Bug Fixes

• xds: Fix an internal bug in xds resource subscription that might cause xds stream not accepting response update for that resource type entirely. (#9810)

v1.52.0

gRPC Java 1.52.0 Release Notes

grpc-xds starting with 1.51.0 had a regression where resources might stop receiving updates. The trigger could happen hours or days after the binary had started. xDS users should avoid this release and use 1.50.x until patch releases with the fix are available. grpc/grpc-java#9809

API Changes

... (truncated)

Commits

• 4ca6de0 Bump version to 1.53.0
• 2a1bb12 Update README etc to reference 1.53.0
• b1b2424 rls:Fix throttling in route lookup (b/262779100) (#9874) (#9879)
• 501ca8f xds: Update logic so that an error being reported when stream is closed gets ...
• b0635fa googleapis: Allow user set c2p bootstrap config (#9856)
• b289519 xds: fixed RouteConfiguration not supporting contain and stringMatcher (#9845)
• 706646f servlet: Implement gRPC server as a Servlet (#8596)
• 44847bf Upgrade JUnit to 4.13.2
• 5a2c94b core: Free unused MessageProducer in RetriableStream
• 9de989b okhttp: Avoid DNS lookup in test
• Additional commits viewable in compare view

Updates io.netty:netty-handler from 4.1.72.Final to 4.1.94.Final

Commits

• da1a448 [maven-release-plugin] prepare release netty-4.1.94.Final
• 535da17 Merge pull request from GHSA-6mjq-h674-j845
• 1bb825b Reuse Bootstrap to create SocketChannel for DNS TCP (#13453)
• dd2c2bb Use Two-Way for finding the delimiter in DelimiterBasedFrameDecoder (#13451)
• 26a7df3 Implement contains for SelectedSelectionKeySet (#13452)
• b878314 Delay possibility to reuse transaction id when query is failing becau… (#13446)
• bf8e779 Simplify DnsQueryContext usage again (#13450)
• 22bf43b Adjust resolver code to make it easier to test in the future (#13445)
• c59a11c Rewrite DnsQueryContextManager to simplify and make it easier to debug (#13440)
• 79c773c Release DnsRecords when failing to notify promise (#13437)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

• Push additional commits to the associated branch.
• Remove the stale label.
• Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

[github-actions]

This PR was closed because it has been stale for 7 days with no activity.

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml