-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency io.grpc:grpc-bom to v1.69.0 #1112
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/grpc-java-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
June 4, 2024 02:01
1a17956
to
3b255ef
Compare
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
June 28, 2024 06:07
3b255ef
to
0317c39
Compare
renovate
bot
changed the title
fix(deps): update dependency io.grpc:grpc-bom to v1.64.0
fix(deps): update dependency io.grpc:grpc-bom to v1.65.0
Jun 28, 2024
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
July 11, 2024 23:11
0317c39
to
8bf3c7c
Compare
renovate
bot
changed the title
fix(deps): update dependency io.grpc:grpc-bom to v1.65.0
fix(deps): update dependency io.grpc:grpc-bom to v1.65.1
Jul 11, 2024
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
August 8, 2024 06:11
8bf3c7c
to
9a0a292
Compare
renovate
bot
changed the title
fix(deps): update dependency io.grpc:grpc-bom to v1.65.1
fix(deps): update dependency io.grpc:grpc-bom to v1.66.0
Aug 8, 2024
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
September 20, 2024 16:42
9a0a292
to
cea8589
Compare
renovate
bot
changed the title
fix(deps): update dependency io.grpc:grpc-bom to v1.66.0
fix(deps): update dependency io.grpc:grpc-bom to v1.68.0
Sep 20, 2024
We are waiting for this release. What is the current status for the new release? |
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
5 times, most recently
from
October 27, 2024 14:54
000b19b
to
fcfa5e9
Compare
renovate
bot
changed the title
fix(deps): update dependency io.grpc:grpc-bom to v1.68.0
Update dependency io.grpc:grpc-bom to v1.68.0
Oct 27, 2024
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
2 times, most recently
from
October 29, 2024 08:41
3e8eb46
to
acf3650
Compare
renovate
bot
changed the title
Update dependency io.grpc:grpc-bom to v1.68.0
Update dependency io.grpc:grpc-bom to v1.68.1
Oct 29, 2024
What is the status of this pull-request? |
renovate
bot
changed the title
Update dependency io.grpc:grpc-bom to v1.68.1
Update dependency io.grpc:grpc-bom to v1.68.2
Nov 28, 2024
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
November 28, 2024 04:16
acf3650
to
8e945b5
Compare
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
December 10, 2024 19:23
8e945b5
to
ccc0fb9
Compare
renovate
bot
changed the title
Update dependency io.grpc:grpc-bom to v1.68.2
Update dependency io.grpc:grpc-bom to v1.69.0
Dec 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
1.63.0
->1.69.0
Release Notes
grpc/grpc-java (io.grpc:grpc-bom)
v1.69.0
v1.68.2
Bug Fixes
Improvements
v1.68.1
v1.68.0 was a mistake. This is the first release of version 1.68.x
Bug Fixes
Behavior Changes
4be69e3
). This is the existing behavior in C core. Duplicate keys in objects are dangerous as which value takes effect is undefined. Previously, the last value was used3a6be9c
). The transport uses two threads, but one is on-demand. If the executor provided tobuilder.transportExecutor()
runs out of threads (e.g., it is a fixed-size thread pool), all transports can be wedged, unable to run on-demand tasks, until keepalive kills one of them. Two threads are now used when handshaking a new transport, and the transport will time out after 1 second with “Timed out waiting for second handshake thread” if two threads are unavailablemesh_id
value fromCSM_MESH_ID
environment variable, instead of getting it from bootstrap file (84d30af
)Improvements
782a44a
) (#11599) (e59ae5f
). This is aio.grpc.Context
storage override to store its state inio.opentelemetry.context.Context
. Libraries should not add a dependency on this artifact, as applications can only have one storage override in their classpathio.grpc.s2a.S2AChannelCredentials
1ded8af
)b692b9d
). This expands the class of bugs that will fail RPCs with the panic error, versus some undefined behaviorfa26a8b
)StreamTracer.inboundMessageRead()
now reports uncompressed message size when the message does not need compression (#11598) (2aae68e
). Previously it always reported-1
(unknown)62f4098
)6f35422
). This is especially helpful when using TLS but not running on AndroidUdsChannelBuilder
, use fake IP instead of localhost (a908b5e
). This avoids an unnecessary DNS lookupf3cf7c3
)99be6e9
)46c1b38
)94a0a0d
)GRPC_EXPERIMENTAL_ENABLE_OTEL_TRACING
environment variable totrue
to enable tracing support inGrpcOpenTelemetry
(#11409, #11477)(043ba55
,421e237
)Dependencies
2ff837a
)Thanks to:
@Juneezee
@lgalfaso
@bestbeforetoday
@hlx502
@JoeCqupt
v1.68.0
: MISTAKEThis was supposed to be v1.67.0, but there was a mistake during the release process. This has everything in v1.67.1, except for:
v1.67.1
gRPC Java 1.67.1 Release Notes
There was no 1.67.0 release. There was a problem making the release and it went to Maven Central as 1.68.0 instead. This is a version-corrected release.
Improvements
90d0fab
)e821d5e
). This makes it clearer whether a leak is a gRPC leak or an application leak when the Detachable API is being used6a9bc3b
)72a977b
)6dbd1b9
)d034a56
)96a788a
)0017c98
)c29763d
)10d6002
). Previously, RLS configuration would not have been updatedBug Fixes
cc1cbe9
)c63e354
)f866c80
). This change applies to all petiole load balancing policies. For regular usages that use dns name resolution, this is unlikely to matter as the default dns name resolver returns consistent addresses. But this might improve LB behavior for some custom load balancers1dae144
)448ec4f
)Dependencies
70ae832
)75012a5
)ff8e413
)Thanks to
@Juneezee
@lujiajing1126
@JarvisCraft
@sunpe
v1.66.0
gRPC Java 1.66.0 Release Notes
API Changes
25a8b7c
)AdvancedTlsX509TrustManager
, anX509ExtendedTrustManager
that allows users to configure advanced TLS features, such as root certificate reloading and peer cert custom verification. (658cbf6
)GracefulSwitchLoadBalancer
config (ebed047
) and mark switchTo() deprecated. (85e0a01
).GracefulSwitchLoadBalancer
now receives its configuration like a regular load balancer.AllowSecurityPolicy
to allow calling code to not have to wait on async/slow implementations.BinderTransport
now submits async implementations to an executor. (#11272) (7fee6a3
)ServerBuilder
for adding a list of service implementations to the handler registry together. (#11285) (85ed053
)Improvements
5ec0187
)36e687f
). There are now examples for both non-bzlmod and bzlmod.PickFirstLeafLoadBalancer
062ebb4
)NettyAdaptiveCumulator
if Netty is on version 4.1.111 or later. (#11367)21dec30
)BinderServer
ownServerAuthInterceptor
's executor that helps avoid leaks. (#11293) (15ad9f5
)ProtoReflectionServiceV1
for the v1 reflection protocol. The preexistingProtoReflectionService
implements the v1alpha reflection protocol. (#11237) (0aa976c
)Bug Fixes
14fd81f
)AdvancedTlsX509TrustManager
validation on servers when using SSLSocket. Previously it would try to use a null SSLEngine . (dcb1c01
)Dependencies
71eb5fb
). This adds a runtime dependency on libstdc++a977385
)a977385
)a977385
)a977385
)a977385
)a977385
)a977385
)a977385
)a977385
)e7c3803
)@com_github_cncf_udpa
usage with preexisting@com_github_cncf_xds
; delete@com_github_cncf_udpa
repo alias for xds (6dd6ca9
)1611a73
(c540993
). The version used by Gradle had been updated in 1.62.0 (68334a0
), but the bazel version had not7a25e68
). Bazel’s protobuf rules no longer use the old com_google_protobuf_javalite repository named3c2f5a
). Protobuf’s targets are generally just used directly; this fixed the only place that used maven’sartifact()
syntaxThanks to
@hlx502
@erm-g
@jdcormie
@JoaoVitorStein
@cfredri4
v1.65.1
What's Changed
v1.65.0
grpc-netty in this release is compatible with Netty 4.1.111; it fixes the incompatibility that caused data corruption. grpc-netty-shaded is still using Netty 4.1.100.
New Features
df8cfe9
)Improvements
ClientStreamTracer.inboundHeaders(Metadata)
(960012d
). This is the same as the existinginboundHeaders()
, but is provided the Metadata6ec744f
)8844cf7
). This could be viewed as a small performance optimization, but mainly reduces the amount of race-handling code781b4c4
) This change shows@ExperimentalApi
being removed, but it was re-added in3c97245
before the releasec31dbf4
)791f894
)Bug fixes
fea577c
). This was a long-standing race that could cause RPCs to hang, but was very unlikely to be hit. Avoiding the double-picking (8844cf7
) made the race more visible0fea7dd
). The previous behavior easily caused data corruptiona28357e
). Previously, shutting down when a new connection was being established could result in the server never becoming terminatede4e7f3a
). This issue was unlikely to be hit outside of specialized testsd57f271
). This fixes a regression introduced in 1.62.234ee600
)1670e97
)f995c12
)Thanks to
@hakusai22
@firov
@mateusazis
@Mir3605
@niloc132
v1.64.2
What's Changed
v1.64.1
What's Changed
v1.64.0
Avoid upgrading your application to Netty 4.1.111, with this version as there is a possible corruption. For Netty 4.1.111 compatibility, it is best to use 1.63.2, 1.64.2, 1.65.1, and later. See https://github.com/grpc/grpc-java/issues/11284 .
API Changes
jakarta_omit
was renamed@generated=omit
(#11086) (8a21afc
)New Features
4561bb5
)5ba1a55
). The feature is still missing documentation and an example. It only supports metrics; tracing and logs will be future enhancements. See gRFC A66d1890c0
)@maven
targets (0064991
)8050723
)06df25b
,35a171b
,2897b39
), to be exported by grpc-opentelemetry if explicitly enabled in GrpcOpenTelemetry. See gRFC A78a9fb272
,a1d1932
,8133318
), to be exported by grpc-opentelemetry if explicitly enabled in GrpcOpenTelemetryImprovements
58de563
)e036b1b
). This will greatly improve the debuggability of certain server errors in particular cases. Instead of the client seeing “CANCELLED: RST_STREAM closed stream. HTTP/2 error code: CANCEL”, they could see “RESOURCE_EXHAUSTED: gRPC message exceeds maximum size4194304
:6144592
”f7ee5f3
)e36f099
)10cb4a3
)537dbe8
)load()
statements for the Bazel builtin top-level java symbols (#11105) (add8c37
)StatusProto.toStatusException
overload to acceptThrowable
(#11083) (5c9b492
)Bug fixes
bdb6230
)2c5f0c2
). Previously the visible state change fromchannel.getState()
was delayed until the name resolver returned results. This had no impact to RPC behaviore630593
)6e97b18
). These races had not been witnessed in practicef9b6e5f
). This fixes a regression introduced by6e97b18
that could hang RPCs instead of using fallback, but fixes a pre-existing bug that could greatly delay RPCs from using fallback.da619e2
). This could have caused backoff entries to improperly be considered expired097a46b
). The credential does its own verification and the default needs to be disabled for SPIFFEfb9a108
)d21fe32
)Dependencies
5a8da19
)c703a1e
)163efa3
)77e59b2
)Acknowledgements
@panchenko
@Ashok-Varma
@benjaminp
@AutomatedTester
@hypnoce
@keith
@laglangyue
@rostik404
@ryanpbrewster
@abtom
@hvadehra
@rtadepalli
v1.63.2
What's Changed
v1.63.1
Bug fixes
fb9a108
)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.