search

buildless / plugin-gradle

Buildless plug-in for Gradle
https://gradle.docs.less.build/
Apache License 2.0
6 stars 5 forks source link

chore(deps): bump grpc_java from 1.56.0 to 1.56.1 #21

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps grpc_java from 1.56.0 to 1.56.1. Updates io.grpc:grpc-api from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


Updates io.grpc:grpc-auth from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


Updates io.grpc:grpc-bom from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


Updates io.grpc:grpc-core from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


Updates io.grpc:grpc-stub from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


Updates io.grpc:grpc-services from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


Updates io.grpc:grpc-testing from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


Updates io.grpc:grpc-netty from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


Updates io.grpc:grpc-protobuf from 1.56.0 to 1.56.1

Release notes

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

v1.56.1

Bug fixes

  • core: Fix regression where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure like "UNAVAILABLE: Unable to resolve host" continuing potentially forever. This did not impact DnsNameResolver, but it did impacted GrpclbNameResolver which is the dns name resolver used when grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.
Commits


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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
sgammon commented 1 year ago

@dependabot rebase

sgammon commented 1 year ago

@dependabot rebase

dependabot[bot] commented 1 year ago

Looks like these dependencies are no longer a dependency, so this is no longer needed.