New version of grpc (1.58.0) produced dependency conflicts

[depfu]

We've tested your project with an updated dependency and got errors while installing the dependencies.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
grpc	~> 1.8	1.58.0

Unfortunately, the build failed while installing dependencies. This means that while the new version is within the specified range, a version conflict between two or more packages will prohibit this version from being installed.

As this breaks fresh installs of your package, we've left this pull request open for you to investigate.

What changed?

✳️ grpc (~> 1.8 → 1.58.0) · Repo · Changelog

Release Notes

1.58.0

This is release 1.58.0 (goku) of gRPC Core.

For gRPC documentation, see grpc.io. For previous releases, see Releases.

This release contains refinements, improvements, and bug fixes, with highlights listed below.

Core

• gRPC 1.58 starts to require c-ares 1.18 or later.
• [Deps] Update boringssl 202308211007. (#34115)
• [pick_first] de-experiment pick first. (#34054)
• [build metadata] Bazel to "other build systems" improvements. (#33803)
• [Deps] Update abseil to 20230802. (#33974)
• [c-ares DNS resolver] Fix file descriptor use-after-close bug when c-ares writes succeed but subsequent read fails. (#33871)

C++

• [docs] Document Alarm thread-safety guarantees. (#34092)
• Added OpenSSL 3.0 (LTS) support via custom CMake builds (the default is still BoringSSL)

Python

• [Bazel] Enable grpcio-reflection to be used via Bazel. (#31013)
• [packaging] Publish xds-protos as part of the standard package pipeline. (#33797)

Ruby

• [ruby] update google auth to ~> 1.0. (#34013)
• [Ruby] set metadata_sent after call success. (#33998)
• [ruby] remove unnecessary background thread startup wait logic that interferes with forking. (#33805)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)