chore(deps): update frauddetectionservice #169
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.25.0
->3.25.5
1.59.0
->1.60.0
By merging this PR, the below vulnerabilities will be automatically resolved:
By merging this PR, the issue #93 will be automatically resolved and closed:
By merging this PR, the below vulnerabilities will be automatically resolved:
Release Notes
grpc/grpc-java (io.grpc:grpc-netty)
v1.60.0
API Changes
ForwardingServerBuilder
,ForwardingChannelBuilder2
, andForwardingChannelBuilder
. Note thatForwardingChannelBuilder
is stabilized (no changes will be made to it), but immediately deprecated in favor ofForwardingChannelBuilder2
. (#10586)ForwardingChannelBuilder.delegate()
. De facto this deprecates the class itself, since all classes extendingForwardingChannelBuilder
implement thedelegate()
method. See javadoc for details (#10587)LoadBalancer.acceptResolvedAddresses()
to returnStatus
instead ofboolean
(#10636). This is part of continued work to align the LB API cross-language and API stabilizationForwardingChannelBuilder2
(#10587)ProtoUtils.metadataMarshaller()
(#10628)Behavior Changes
ManagedChannel
s now check the address types provided by the nameResolver (for the given target) with the address types supported by the channel transport and generate an error in case of mismatch. That dramatically improves the error message when an issue occursStatus.UNKNOWN
returned to the client will haveApplication error processing RPC
description. Previously the description was empty. This is helpful to differentiate between server errors originated in user application, gRPC library, or even those injected by a proxy. (#10643)Improvements
Http2Headers.isEmpty()
. This fixes compatibility with Netty 4.1.101.Final.NettyServerBuilder.maxRstFramesPerWindow()
. This can be used to limit impact of Rapid ResetBug Fixes
Dependencies
Acknowledgements
@anthonyjpratti
@fedorka
@jpd236
@mateusazis
@pkoenig10
@yannickepstein
@amirhadadi
v1.59.1
Http2Headers.isEmpty()
. This fixes compatibility with Netty 4.1.101.Final.NettyServerBuilder.maxRstFramesPerWindow()
. This can be used to limit impact of Rapid Reset