Sourced from io.grpc:grpc-netty-shaded's releases.

v1.75.0

Behavior Changes

• binder: Introduce server pre-authorization (#12127). grpc-binder clients authorize servers by checking the UID of the sender of the SETUP_TRANSPORT Binder transaction against some SecurityPolicy. But merely binding to an unauthorized server to learn its UID can enable "keep-alive" and "background activity launch" abuse, even if security policy ultimately causes the grpc connection to fail. Pre-authorization mitigates this kind of abuse by resolving addresses and authorizing a candidate server Application's UID before binding to it. Pre-auth is especially important when the server's address is not fixed in advance but discovered by PackageManager lookup.

Bug Fixes

• core: grpc-timeout should always be positive (#12201) (6dfa03c51). There is a local race between when the deadline is checked before sending the RPC and when the timeout is calculated to put on-the-wire. The code replaced negative timeouts with 0 nanoseconds. gRPC’s PROTOCOL-HTTP2 spec states that timeouts should be positive, so now non-positive values are replaced with 1 nanosecond
• core: Improved DEADLINE_EXCEEDED message for delayed calls (6ff8ecac0). Delayed calls are the first calls on a Channel before name resolution has resolved addresses. Previously you could see confusing errors saying the deadline “will be exceeded in” X time. The message tense was simply wrong, and now will be correct: deadline “was exceeded after” X time.
• xds: PriorityLB now only uses the failOverTimer to start additional priorities, not fail RPCs (c4256add4). You should no longer see “Connection timeout for priority” errors.

Improvements

• netty: Count sent RST_STREAMs against NettyServerBuilder.maxRstFramesPerWindow() limit (#12288). This extends the Rapid Reset tool to also cover MadeYouReset. the reset stream count will cause a 420 "Enhance your calm response" to be sent. This depends on Netty 4.1.124 for a bug fix to actually call the encoder by the frame writer.
• xds: Convert CdsLb to XdsDepManager (297ab05ef). This is part of gRFC A74 to have atomic xDS config updates. This is an internal change, but does change the error description seen in certain cases, especially DEADLINE_EXCEEDED on a brand-new channel.
• census: APIs for stats and tracing (#12050) (919370172). Client channel and server builders with interceptors and factories respectively for stats and tracing.
• stub: simplify BlockingClientCall infinite blocking (#12217) (ba0a7329d). Move deadline computation into overloads with finite timeouts. Blocking calls without timeouts now do not have to read the clock.
• xds: Do RLS fallback policy eagar start (#12211) (42e1829b3). In gRPC-Java, the xDS clusters were lazily subscribed, which meant the fallback target which is returned in the RLS config wasn’t subscribed until a RPC actually falls back to it. The delayed resource subscription process in gRPC Java made it more susceptible to the effects of the INITIAL_RESOURCE_FETCH_TIMEOUT compared to other programming languages. It also had impact beyond the RLS cache expiration case, for example, when the first time the client initialized the channel, we couldn't fallback when the intended target times out, because of the lazy subscription. This change starts the fallback LB policy for the default target at the start of RLS policy instead of only when falling back to the default target, which fixes the above mentioned problems.
• xds: Aggregate cluster fixes (A75) (#12186) (7e982e48a). The earlier implementation of aggregate clusters concatenated the priorities from the underlying clusters into a single list, so that it could use a single LB policy defined at the aggregate cluster layer to choose a priority from that combined list. However, it turns out that aggregate clusters don't actually define the LB policy in the aggregate cluster; instead, the aggregate cluster uses a special cluster-provided LB policy that first chooses the underlying cluster and then delegates to the LB policy of the underlying cluster. This change implements that.
• api: set size correctly for sets and maps in handling Metadata values to be exchanged during a call (#12229) (80217275d)
• xds: xdsClient cache transient error for new watchers (#12291). When a resource update is NACKed, cache the error and update new watchers that get added with that error instead of making them hang.
• xds: Avoid PriorityLb re-enabling timer on duplicate CONNECTING (#12289). If a LB policy gives extraneous updates with state CONNECTING, then it was possible to re-create failOverTimer which would then wait the 10 seconds for the child to finish CONNECTING. We only want to give the child one opportunity after transitioning out of READY/IDLE.
• xds: Use a different log name for XdsClientImpl and ControlPlaneClient (#12287). ControlPlaneClient uses "xds-cp-client" now instead of "xds-client" while logging.

Dependencies Changes

• Upgrade to Netty 4.1.124.Final (#12286). This implicitly disables NettyAdaptiveCumulator (#11284), which can have a performance impact. We delayed upgrading Netty to give time to rework the optimization, but we've gone too long already without upgrading which causes problems for vulnerability tracking.
• bazel: Use jar_jar to avoid xds deps (#12243) (8f09b9689). The //xds and //xds:orca targets now use jar_jar to shade the protobuf generated code. This allows them to use their own private copy of the protos and drop direct Bazel dependencies on cel-spec, grpc, rules_go, com_github_cncf_xds, envoy_api, com_envoyproxy_protoc_gen_validate, and opencensus_proto. This mirrors the shading of protobuf messages done for grpc-xds provided on Maven Central and should simplify dependency management
• Protobuf upgraded to 3.25.8
• proto-google-common-protos upgraded to 2.59.2
• s2a-proto upgraded to 1.1.2
• google-cloud-logging upgraded to 3.23.1 (used by gcp-observability)
• OpenTelemetry upgraded to 1.52.0

Documentation

• Clarify requirements for creating a cross-user Channel. (#12181). The @SystemApi runtime visibility requirement isn't really new. It has always been implicit in the required INTERACT_ACROSS_USERS permission, which can only be held by system apps in production. Now deprecated BinderChannelBuilder#bindAsUser has always required SDK_INT >= 30. This change just copies that requirement forward to its replacement APIs in AndroidComponentAddress and the TARGET_ANDROID_USER NameResolver.Args.
• api: Add more Javadoc for NameResolver.Listener2 interface (#12220) (d352540a0)

Thanks to

@​benjaminp @​werkt @​kilink @​vimanikag

v1.74.0

Behavior Changes

• compiler: Default to @generated=omit (f8700a13a). This omits javax.annotation.Generated from the generated code and makes the org.apache.tomcat:annotations-api compile-only dependency unnecessary (README and examples changes forthcoming; we delayed those changes until the release landed). You can use the option @generated=javax for the previous behavior, but please also file an issue so we can develop alternatives
• compiler: generate blocking v2 unary calls that throw StatusException (#12126) (a16d65591). Previously, the new blocking stub API was identical to the older blocking stub for unary RPCs and used the unchecked StatusRuntimeException. However, feedback demonstrated it was confusing to mix that with the checked StatusException in BlockingClientCall. Now the new blocking stub uses StatusException throughout. grpc-java continues to support the old generated code, but the version of protoc-gen-grpc-java will dictate which API you see. If you support multiple generated code versions, you can use the older blocking v1 stub for unary RPCs

Bug Fixes

• netty: Fix a race that caused RPCs to hang on start when a GOAWAY was received while the RPCs’ headers were being written to the OS (b04c673fd, 15c757398). This was a very old race, not a recent regression. All streams should now properly fail instead of hanging, although in some cases they may be transparently retried

... (truncated)

• 3abc0e6 Bump version to 1.75.0
• cbfe6c1 Update README etc to reference 1.75.0
• a0f3520 Revert "Release v1.75.0 (#12294)" (#12295)
• 7ef13f4 Release v1.75.0 (#12294)
• 14fd8ef xds: xdsClient caches transient error for new watchers (v1.75.x backport) (#1...
• 653d076 xds: Avoid PriorityLb re-enabling timer on duplicate CONNECTING (#12289)
• a5c2b1a netty: Count sent RST_STREAMs against limit (1.75.x backport) (#12288)
• 0d3e828 xds: Use a different log name for XdsClientImpl and ControlPlaneClient (1.75....
• d750e9d Upgrade to Netty 4.1.124.Final (v1.75.x backport) (#12286)
• 19c579e Bump versions of dependencies (#12252)
• Additional commits viewable in compare view

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

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

C++

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

Protocol Buffers v3.18.3

C++

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

• 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

Sourced from org.hibernate.validator:hibernate-validator's changelog.

6.2.0.Final (23-12-2020)

** Bug * HV-1821 - engine - HV-1755 introduces NPE in org.hibernate.validator.internal.engine.ValidatorFactoryImpl constructor

** New Feature * HV-1822 - validators - Add Russian specific validator for russian taxpayer identification number

6.2.0.CR1 (07-12-2020)

** Improvement * HV-1812 - engine - Avoid reflection-based metadata extraction for built-in value extractors

** New Feature * HV-1816 - engine - Disable Expression Language by default for custom constraint violations

** Remove Feature * HV-1790 - engine, validators - Remove the SafeHtml constraint

** Task * HV-1820 - engine - Upgrade JBoss Logging to 3.4.1.Final * HV-1819 - engine - Upgrade Classmate to 1.5.1 * HV-1817 - build - Upgrade to checkstyle 8.38

6.1.6.Final (30-09-2020)

** Bug * HV-1804 - translations - Fix Dutch translation for @​Size constraint * HV-1797 - validators - Validation on classes with a bidirectional relationship cause stack overflow on 6.1.x * HV-1761 - engine - Interpolation of primitive arrays causes a ClassCastException

** Improvement * HV-1782 - translations - Remove trailing dot from @​Max constraint German translation

** New Feature * HV-1780 - validators - Add @​Normalized contraint that validates if text is normalized in a given form

** Task * HV-1803 - tests - Move the tests to log4j2 * HV-1802 - tests - Update ByteBuddy test dependency to 1.10.16 * HV-1795 - build - Remove link to JavaMoney javadoc

6.1.5.Final (06-05-2020)

** Bug * HV-1774 - engine - Invalid parsing of EL expression can lead to invalid EL expressions considered valid

... (truncated)

• a883dcd [Jenkins release job] Preparing release 6.2.0.Final
• badcc8f [Jenkins release job] changelog.txt updated by release build 6.2.0.Final
• ff4faab [Jenkins release job] README.md updated by release build 6.2.0.Final
• d8c8faa HV-1822 add russian specific INN annotation
• 3304647 HV-1821 Support using a non-Hibernate Validator configuration class
• 9c61b95 [Jenkins release job] Preparing next development iteration
• 02ed74e [Jenkins release job] Preparing release 6.2.0.CR1
• 401a85d [Jenkins release job] changelog.txt updated by release build 6.2.0.CR1
• 7232226 [Jenkins release job] README.md updated by release build 6.2.0.CR1
• 1785054 HV-1820 Upgrade JBoss Logging to 3.4.1.Final
• Additional commits viewable in compare view

Sourced from io.pebbletemplates:pebble's releases.

3.2.4

3.2.3

3.2.2

3.2.1

3.2.0

• 005e1af [maven-release-plugin] prepare for next development iteration
• 6cb1a88 [maven-release-plugin] prepare release v3.2.4
• a824b04 Slow VM
• 9e218a0 Add changelog
• 6c76a54 Buy me a coffee
• 84abcf0 Fix the problem of unit test failure under JDK 21 (#692)
• 4105d2c Fix the problem of not resolving reactive values in models (#691)
• 948362b [maven-release-plugin] prepare for next development iteration
• a7f89e3 [maven-release-plugin] prepare release v3.2.3
• d5bcd35 Update nexus plugin for release
• Additional commits viewable in compare view

Sourced from io.grpc:grpc-netty-shaded's releases.

v1.75.0

Behavior Changes

• binder: Introduce server pre-authorization (#12127). grpc-binder clients authorize servers by checking the UID of the sender of the SETUP_TRANSPORT Binder transaction against some SecurityPolicy. But merely binding to an unauthorized server to learn its UID can enable "keep-alive" and "background activity launch" abuse, even if security policy ultimately causes the grpc connection to fail. Pre-authorization mitigates this kind of abuse by resolving addresses and authorizing a candidate server Application's UID before binding to it. Pre-auth is especially important when the server's address is not fixed in advance but discovered by PackageManager lookup.

Bug Fixes

• core: grpc-timeout should always be positive (#12201) (6dfa03c51). There is a local race between when the deadline is checked before sending the RPC and when the timeout is calculated to put on-the-wire. The code replaced negative timeouts with 0 nanoseconds. gRPC’s PROTOCOL-HTTP2 spec states that timeouts should be positive, so now non-positive values are replaced with 1 nanosecond
• core: Improved DEADLINE_EXCEEDED message for delayed calls (6ff8ecac0). Delayed calls are the first calls on a Channel before name resolution has resolved addresses. Previously you could see confusing errors saying the deadline “will be exceeded in” X time. The message tense was simply wrong, and now will be correct: deadline “was exceeded after” X time.
• xds: PriorityLB now only uses the failOverTimer to start additional priorities, not fail RPCs (c4256add4). You should no longer see “Connection timeout for priority” errors.

Improvements

• netty: Count sent RST_STREAMs against NettyServerBuilder.maxRstFramesPerWindow() limit (#12288). This extends the Rapid Reset tool to also cover MadeYouReset. the reset stream count will cause a 420 "Enhance your calm response" to be sent. This depends on Netty 4.1.124 for a bug fix to actually call the encoder by the frame writer.
• xds: Convert CdsLb to XdsDepManager (297ab05ef). This is part of gRFC A74 to have atomic xDS config updates. This is an internal change, but does change the error description seen in certain cases, especially DEADLINE_EXCEEDED on a brand-new channel.
• census: APIs for stats and tracing (#12050) (919370172). Client channel and server builders with interceptors and factories respectively for stats and tracing.
• stub: simplify BlockingClientCall infinite blocking (#12217) (ba0a7329d). Move deadline computation into overloads with finite timeouts. Blocking calls without timeouts now do not have to read the clock.
• xds: Do RLS fallback policy eagar start (#12211) (42e1829b3). In gRPC-Java, the xDS clusters were lazily subscribed, which meant the fallback target which is returned in the RLS config wasn’t subscribed until a RPC actually falls back to it. The delayed resource subscription process in gRPC Java made it more susceptible to the effects of the INITIAL_RESOURCE_FETCH_TIMEOUT compared to other programming languages. It also had impact beyond the RLS cache expiration case, for example, when the first time the client initialized the channel, we couldn't fallback when the intended target times out, because of the lazy subscription. This change starts the fallback LB policy for the default target at the start of RLS policy instead of only when falling back to the default target, which fixes the above mentioned problems.
• xds: Aggregate cluster fixes (A75) (#12186) (7e982e48a). The earlier implementation of aggregate clusters concatenated the priorities from the underlying clusters into a single list, so that it could use a single LB policy defined at the aggregate cluster layer to choose a priority from that combined list. However, it turns out that aggregate clusters don't actually define the LB policy in the aggregate cluster; instead, the aggregate cluster uses a special cluster-provided LB policy that first chooses the underlying cluster and then delegates to the LB policy of the underlying cluster. This change implements that.
• api: set size correctly for sets and maps in handling Metadata values to be exchanged during a call (#12229) (80217275d)
• xds: xdsClient cache transient error for new watchers (#12291). When a resource update is NACKed, cache the error and update new watchers that get added with that error instead of making them hang.
• xds: Avoid PriorityLb re-enabling timer on duplicate CONNECTING (#12289). If a LB policy gives extraneous updates with state CONNECTING, then it was possible to re-create failOverTimer which would then wait the 10 seconds for the child to finish CONNECTING. We only want to give the child one opportunity after transitioning out of READY/IDLE.
• xds: Use a different log name for XdsClientImpl and ControlPlaneClient (#12287). ControlPlaneClient uses "xds-cp-client" now instead of "xds-client" while logging.

Dependencies Changes

• Upgrade to Netty 4.1.124.Final (#12286). This implicitly disables NettyAdaptiveCumulator (#11284), which can have a performance impact. We delayed upgrading Netty to give time to rework the optimization, but we've gone too long already without upgrading which causes problems for vulnerability tracking.
• bazel: Use jar_jar to avoid xds deps (#12243) (8f09b9689). The //xds and //xds:orca targets now use jar_jar to shade the protobuf generated code. This allows them to use their own private copy of the protos and drop direct Bazel dependencies on cel-spec, grpc, rules_go, com_github_cncf_xds, envoy_api, com_envoyproxy_protoc_gen_validate, and opencensus_proto. This mirrors the shading of protobuf messages done for grpc-xds provided on Maven Central and should simplify dependency management
• Protobuf upgraded to 3.25.8
• proto-google-common-protos upgraded to 2.59.2
• s2a-proto upgraded to 1.1.2
• google-cloud-logging upgraded to 3.23.1 (used by gcp-observability)
• OpenTelemetry upgraded to 1.52.0

Documentation

• Clarify requirements for creating a cross-user Channel. (#12181). The @SystemApi runtime visibility requirement isn't really new. It has always been implicit in the required INTERACT_ACROSS_USERS permission, which can only be held by system apps in production. Now deprecated BinderChannelBuilder#bindAsUser has always required SDK_INT >= 30. This change just copies that requirement forward to its replacement APIs in AndroidComponentAddress and the TARGET_ANDROID_USER NameResolver.Args.
• api: Add more Javadoc for NameResolver.Listener2 interface (#12220) (d352540a0)

Thanks to

@​benjaminp @​werkt @​kilink @​vimanikag

v1.74.0

Behavior Changes

• compiler: Default to @generated=omit (f8700a13a). This omits javax.annotation.Generated from the generated code and makes the org.apache.tomcat:annotations-api compile-only dependency unnecessary (README and examples changes forthcoming; we delayed those changes until the release landed). You can use the option @generated=javax for the previous behavior, but please also file an issue so we can develop alternatives
• compiler: generate blocking v2 unary calls that throw StatusException (#12126) (a16d65591). Previously, the new blocking stub API was identical to the older blocking stub for unary RPCs and used the unchecked StatusRuntimeException. However, feedback demonstrated it was confusing to mix that with the checked StatusException in BlockingClientCall. Now the new blocking stub uses StatusException throughout. grpc-java continues to support the old generated code, but the version of protoc-gen-grpc-java will dictate which API you see. If you support multiple generated code versions, you can use the older blocking v1 stub for unary RPCs

Bug Fixes

• netty: Fix a race that caused RPCs to hang on start when a GOAWAY was received while the RPCs’ headers were being written to the OS (b04c673fd, 15c757398). This was a very old race, not a recent regression. All streams should now properly fail instead of hanging, although in some cases they may be transparently retried

... (truncated)

• 3abc0e6 Bump version to 1.75.0
• cbfe6c1 Update README etc to reference 1.75.0
• a0f3520 Revert "Release v1.75.0 (#12294)" (#12295)
• 7ef13f4 Release v1.75.0 (#12294)
• 14fd8ef xds: xdsClient caches transient error for new watchers (v1.75.x backport) (#1...
• 653d076 xds: Avoid PriorityLb re-enabling timer on duplicate CONNECTING (#12289)
• a5c2b1a netty: Count sent RST_STREAMs against limit (1.75.x backport) (#12288)
• 0d3e828 xds: Use a different log name for XdsClientImpl and ControlPlaneClient (1.75....
• d750e9d Upgrade to Netty 4.1.124.Final (v1.75.x backport) (#12286)
• 19c579e Bump versions of dependencies (#12252)
• Additional commits viewable in compare view

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

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

C++

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

Protocol Buffers v3.18.3

C++

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

• 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

Sourced from io.grpc:grpc-netty-shaded's releases.

v1.75.0

Behavior Changes

• binder: Introduce server pre-authorization (#12127). grpc-binder clients authorize servers by checking the UID of the sender of the SETUP_TRANSPORT Binder transaction against some SecurityPolicy. But merely binding to an unauthorized server to learn its UID can enable "keep-alive" and "background activity launch" abuse, even if security policy ultimately causes the grpc connection to fail. Pre-authorization mitigates this kind of abuse by resolving addresses and authorizing a candidate server Application's UID before binding to it. Pre-auth is especially important when the server's address is not fixed in advance but discovered by PackageManager lookup.

Bug Fixes

• core: grpc-timeout should always be positive (#12201) (6dfa03c51). There is a local race between when the deadline is checked before sending the RPC and when the timeout is calculated to put on-the-wire. The code replaced negative timeouts with 0 nanoseconds. gRPC’s PROTOCOL-HTTP2 spec states that timeouts should be positive, so now non-positive values are replaced with 1 nanosecond
• core: Improved DEADLINE_EXCEEDED message for delayed calls (6ff8ecac0). Delayed calls are the first calls on a Channel before name resolution has resolved addresses. Previously you could see confusing errors saying the deadline “will be exceeded in” X time. The message tense was simply wrong, and now will be correct: deadline “was exceeded after” X time.
• xds: PriorityLB now only uses the failOverTimer to start additional priorities, not fail RPCs (c4256add4). You should no longer see “Connection timeout for priority” errors.

Improvements

• netty: Count sent RST_STREAMs against NettyServerBuilder.maxRstFramesPerWindow() limit (#12288). This extends the Rapid Reset tool to also cover MadeYouReset. the reset stream count will cause a 420 "Enhance your calm response" to be sent. This depends on Netty 4.1.124 for a bug fix to actually call the encoder by the frame writer.
• xds: Convert CdsLb to XdsDepManager (297ab05ef). This is part of gRFC A74 to have atomic xDS config updates. This is an internal change, but does change the error description seen in certain cases, especially DEADLINE_EXCEEDED on a brand-new channel.
• census: APIs for stats and tracing (#12050) (919370172). Client channel and server builders with interceptors and factories respectively for stats and tracing.
• stub: simplify BlockingClientCall infinite blocking (#12217) (ba0a7329d). Move deadline computation into overloads with finite timeouts. Blocking calls without timeouts now do not have to read the clock.
• xds: Do RLS fallback policy eagar start (#12211) (42e1829b3). In gRPC-Java, the xDS clusters were lazily subscribed, which meant the fallback target which is returned in the RLS config wasn’t subscribed until a RPC actually falls back to it. The delayed resource subscription process in gRPC Java made it more susceptible to the effects of the INITIAL_RESOURCE_FETCH_TIMEOUT compared to other programming languages. It also had impact beyond the RLS cache expiration case, for example, when the first time the client initialized the channel, we couldn't fallback when the intended target times out, because of the lazy subscription. This change starts the fallback LB policy for the default target at the start of RLS policy instead of only when falling back to the default target, which fixes the above mentioned problems.
• xds: Aggregate cluster fixes (A75) (#12186) (7e982e48a). The earlier implementation of aggregate clusters concatenated the priorities from the underlying clusters into a single list, so that it could use a single LB policy defined at the aggregate cluster layer to choose a priority from that combined list. However, it turns out that aggregate clusters don't actually define the LB policy in the aggregate cluster; instead, the aggregate cluster uses a special cluster-provided LB policy that first chooses the underlying cluster and then delegates to the LB policy of the underlying cluster. This change implements that.
• api: set size correctly for sets and maps in handling Metadata values to be exchanged during a call (#12229) (80217275d)
• xds: xdsClient cache transient error for new watchers (#12291). When a resource update is NACKed, cache the error and update new watchers that get added with that error instead of making them hang.
• xds: Avoid PriorityLb re-enabling timer on duplicate CONNECTING (#12289). If a LB policy gives extraneous updates with state CONNECTING, then it was possible to re-create failOverTimer which would then wait the 10 seconds for the child to finish CONNECTING. We only want to give the child one opportunity after transitioning out of READY/IDLE.
• xds: Use a different log name for XdsClientImpl and ControlPlaneClient (#12287). ControlPlaneClient uses "xds-cp-client" now instead of "xds-client" while logging.

Dependencies Changes

• Upgrade to Netty 4.1.124.Final (#12286). This implicitly disables NettyAdaptiveCumulator (#11284), which can have a performance impact. We delayed upgrading Netty to give time to rework the optimization, but we've gone too long already without upgrading which causes problems for vulnerability tracking.
• bazel: Use jar_jar to avoid xds deps (#12243) (8f09b9689). The //xds and //xds:orca targets now use jar_jar to shade the protobuf generated code. This allows them to use their own private copy of the protos and drop direct Bazel dependencies on cel-spec, grpc, rules_go, com_github_cncf_xds, envoy_api, com_envoyproxy_protoc_gen_validate, and opencensus_proto. This mirrors the shading of protobuf messages done for grpc-xds provided on Maven Central and should simplify dependency management
• Protobuf upgraded to 3.25.8
• proto-google-common-protos upgraded to 2.59.2
• s2a-proto upgraded to 1.1.2
• google-cloud-logging upgraded to 3.23.1 (used by gcp-observability)
• OpenTelemetry upgraded to 1.52.0

Documentation

• Clarify requirements for creating a cross-user Channel. (#12181). The @SystemApi runtime visibility requirement isn't really new. It has always been implicit in the required INTERACT_ACROSS_USERS permission, which can only be held by system apps in production. Now deprecated BinderChannelBuilder#bindAsUser has always required SDK_INT >= 30. This change just copies that requirement forward to its replacement APIs in AndroidComponentAddress and the TARGET_ANDROID_USER NameResolver.Args.
• api: Add more Javadoc for NameResolver.Listener2 interface (#12220) (d352540a0)

Thanks to

@​benjaminp @​werkt @​kilink @​vimanikag

v1.74.0

Behavior Changes

• compiler: Default to @generated=omit (f8700a13a). This omits javax.annotation.Generated from the generated code and makes the org.apache.tomcat:annotations-api compile-only dependency unnecessary (README and examples changes forthcoming; we delayed those changes until the release landed). You can use the option @generated=javax for the previous behavior, but please also file an issue so we can develop alternatives
• compiler: generate blocking v2 unary calls that throw StatusException (#12126) (a16d65591). Previously, the new blocking stub API was identical to the older blocking stub for unary RPCs and used the unchecked StatusRuntimeException. However, feedback demonstrated it was confusing to mix that with the checked StatusException in BlockingClientCall. Now the new blocking stub uses StatusException throughout. grpc-java continues to support the old generated code, but the version of protoc-gen-grpc-java will dictate which API you see. If you support multiple generated code versions, you can use the older blocking v1 stub for unary RPCs

Bug Fixes

• netty: Fix a race that caused RPCs to hang on start when a GOAWAY was received while the RPCs’ headers were being written to the OS (b04c673fd, 15c757398). This was a very old race, not a recent regression. All streams should now properly fail instead of hanging, although in some cases they may be transparently retried

... (truncated)

• 3abc0e6 Bump version to 1.75.0
• cbfe6c1 Update README etc to reference 1.75.0
• a0f3520 Revert "Release v1.75.0 (#12294)" (#12295)
• 7ef13f4 Release v1.75.0 (#12294)
• 14fd8ef xds: xdsClient caches transient error for new watchers (v1.75.x backport) (#1...
• 653d076 xds: Avoid PriorityLb re-enabling timer on duplicate CONNECTING (#12289)
• a5c2b1a netty: Count sent RST_STREAMs against limit (1.75.x backport) (#12288)
• 0d3e828 xds: Use a different log name for XdsClientImpl and ControlPlaneClient (1.75....
• d750e9d Upgrade to Netty 4.1.124.Final (v1.75.x backport) (#12286)
• 19c579e Bump versions of dependencies (#12252)
• Additional commits viewable in compare view

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

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

C++

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

Protocol Buffers v3.18.3

C++

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

• 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

Sourced from org.hibernate.validator:hibernate-validator's changelog.

6.2.0.Final (23-12-2020)

**...

Description has been truncated