This repository was archived by the owner on Sep 18, 2023. It is now read-only.
deps: update dependency io.grpc:grpc-bom to v1.37.0#131
Merged
gcf-merge-on-green[bot] merged 1 commit intogoogleapis:masterfrom Apr 12, 2021
Merged
Conversation
923476e to
4c17c65
Compare
Neenu1995
approved these changes
Apr 12, 2021
gcf-merge-on-green bot
pushed a commit
that referenced
this pull request
May 12, 2021
🤖 I have created a release \*beep\* \*boop\* --- ## [2.2.0](https://www.github.com/googleapis/java-common-protos/compare/v2.1.0...v2.2.0) (2021-05-12) ### Features * **generator:** update protoc to v3.15.3 ([#123](https://www.github.com/googleapis/java-common-protos/issues/123)) ([6e4c513](https://www.github.com/googleapis/java-common-protos/commit/6e4c513c736d03deddd4d61d98969a866e2a2600)) * introduce google.type.Decimal ([#133](https://www.github.com/googleapis/java-common-protos/issues/133)) ([2602033](https://www.github.com/googleapis/java-common-protos/commit/2602033ac638869765c331a6431940302c0a9147)) * Publish visibility.proto ([#148](https://www.github.com/googleapis/java-common-protos/issues/148)) ([70a872e](https://www.github.com/googleapis/java-common-protos/commit/70a872e3cdf3141d745028f4774574019c2eb7df)) ### Bug Fixes * correct maven artifact metadata ([#145](https://www.github.com/googleapis/java-common-protos/issues/145)) ([15f5c4a](https://www.github.com/googleapis/java-common-protos/commit/15f5c4a51124ce2d193f3947c1ef63710e25e7af)), closes [#72](https://www.github.com/googleapis/java-common-protos/issues/72) * release scripts from issuing overlapping phases ([#142](https://www.github.com/googleapis/java-common-protos/issues/142)) ([36fedec](https://www.github.com/googleapis/java-common-protos/commit/36fedec9122adf95dfc4171311d4161867f8c8a6)) * typo ([#140](https://www.github.com/googleapis/java-common-protos/issues/140)) ([e05c3f9](https://www.github.com/googleapis/java-common-protos/commit/e05c3f9ada5fe444dd782dd7297b210e6c617b10)) ### Documentation * correct label format for monitored_resource and log_entry labels for managed monitored_resource should not have forward slash labels for log_entry should not have forward slash ([#128](https://www.github.com/googleapis/java-common-protos/issues/128)) ([05cfd8c](https://www.github.com/googleapis/java-common-protos/commit/05cfd8ca8f574502aa66b5be491eaaf7c1a01539)) ### Dependencies * update dependency com.google.protobuf:protobuf-bom to v3.15.6 ([#122](https://www.github.com/googleapis/java-common-protos/issues/122)) ([3fe8289](https://www.github.com/googleapis/java-common-protos/commit/3fe8289816924b9d4fdcefa49f225fc456c44064)) * update dependency com.google.protobuf:protobuf-bom to v3.15.8 ([#137](https://www.github.com/googleapis/java-common-protos/issues/137)) ([e3315de](https://www.github.com/googleapis/java-common-protos/commit/e3315debecbfd08db73b9c7303e0760024ff7504)) * update dependency com.google.protobuf:protobuf-bom to v3.16.0 ([#152](https://www.github.com/googleapis/java-common-protos/issues/152)) ([fe2b858](https://www.github.com/googleapis/java-common-protos/commit/fe2b8584a72cd8ca2adeb311f2a4b5cd2b642983)) * update dependency io.grpc:grpc-bom to v1.37.0 ([#131](https://www.github.com/googleapis/java-common-protos/issues/131)) ([5f6476a](https://www.github.com/googleapis/java-common-protos/commit/5f6476a8d3c88f97aa033b95b65d65b9a2de1421)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.36.0->1.37.0Release Notes
grpc/grpc-java
v1.37.0Compare Source
Behavior Changes
GoogleDefaultChannelCredentialsandComputeEngineChannelCredentialschoose ALTS for backends given by xDS TD. Changes forComputeEngineChannelCredentialswere missing, but they really should be the same.ServerBuilder.addServices()API that allows adding a list of services instead of iterating through list and callingaddService().NameResolverAPIs that have been marked as deprecated since 1.21 release.ChannelzandCSDSwith dependencies required at runtime.pendingDeadline.cancelout of synchronized block.channel.shutdown(). PreviouslyshutdownNow()was required for prompt shutdown if a connection was handshaking.io.grpc.xds.bootstrapConfig.server_listener_resource_name_templateproperty from the bootstrap file for server side xDS processing as per the gRFC A36-xds-for-servers.md.New Features
TlsChannelCredentialsandTlsServerCredentialsnow support client certificates and custom KeyManagers/TrustManagers. grpc-netty fully supports these options. grpc-okhttp does not support keyfile-based configuration; you’d need to use a KeyManager. Most users of Netty’s SslContext and GrpcSslContexts should be able to migrate and are encouraged to do so, because this API does not have a Netty dependency and so is planned to become stable.XdsServingStatusListenerhas been implemented as per the gRFC A36-xds-for-servers.md.CsdsService. It is safe for production but are Experimental APIs to resolve issues discovered as they see usage. The rationale and description of the new API can be found in gRFC A40: xDS Configuration Dump via Client Status Discovery Service in gRPC.WeightedTargetLoadBalancercollect all failure child pickers to log more error details.Bug Fixes
TRANSIENT_FAILUREfor such cases.CdsLoadBalancer2childLb shutdown behavior. Previously these childLbs are not properly shutdown, which might cause channel panic as client channel is referenced by those childLbs.UnsupportedOperationExceptionincompatibility with Netty 4.1.60.Final (#7953). This allows users of grpc-netty that may be using Netty elsewhere in their application to upgrade their Netty version to avoid exposure to recent Netty CVEs. gRPC itself is not impacted by those CVEs.CONNECTINGsubchannels when aggregating the overall LB state, which would cause RPCs to fail prematurely if there are subchannels in its initial connection.AltsTestServerobject lock, this way, alts client and alts server won’t race on theAltsTestServerduring Alts handshake negotiation.Documentation
TlsChannelCredentials/TlsServerCredentialsand no longer depends on Netty at compile time.Dependencies
ac9a26373. Added xDS v3 csds.proto with dependencies.Acknowledgements
@spkrka Kristofer Karlsson
@njhill Nick Hill
@ulfjack Ulf Adams
v1.36.1Compare Source
UnsupportedOperationExceptionincompatibility with Netty 4.1.60.Final (#7953). This allows users of grpc-netty that may be using Netty elsewhere in their application to upgrade their Netty version to avoid exposure to recent Netty CVEs. gRPC is not impacted by those CVEs so a Netty upgrade for gRPC itself is not necessaryio.grpc.xds.bootstrapValuesystem property toio.grpc.xds.bootstrapConfig. This more closely matches the environment variable (GRPC_XDS_BOOTSTRAP_CONFIG) and avoids future confusion (#7968)IllegalStateExceptioncausing Channel panic during LB shutdown (#7942). The bug was introduced in v1.36.0. The issue likely most impacts xDS users that may leave a channel unused (no RPCs) for 30 minutes since idle timeout triggers LB shutdownConfiguration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.