Skip to content

Upgrade tonic dependencies to 0.13.0 version #7377

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rmn-boiko
Copy link

Which issue does this PR close?

Upgrade version of tonic used in dependencies from 0.12.3 to 0.13.0, which includes a batch of breaking changes.

Rationale for this change

Using the latest version of crates will prevent any potential issues and vulnerabilities. And will allow users to use latest tonic with arrow crates without keeping different versions

What changes are included in this PR?

Updated the new interface names.
Changed feature names used in the latest tonic.
Updated GitHub workflows to run tests correctly with the required tonic features.

@github-actions github-actions bot added arrow Changes to the arrow crate arrow-flight Changes to the arrow-flight crate labels Apr 2, 2025
@alamb
Copy link
Contributor

alamb commented Apr 3, 2025

Thank you @rmn-boiko -- looks like there are a few CI failures yet to fix, but otherwise 💯

@rmn-boiko
Copy link
Author

rmn-boiko commented Apr 4, 2025

Have to hold this PR until prost will support latest tonic version
tokio-rs/prost#1264

@rmn-boiko rmn-boiko force-pushed the upgrade-tonic-version branch from 047326a to 5b6c22d Compare April 22, 2025 11:03
@rmn-boiko
Copy link
Author

rmn-boiko commented Apr 22, 2025

I've updated PR with the latest codegen changes. Will wait for comments
Also, I had to add a default CryptoProvider(I chose ring as the most suitable here)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arrow Changes to the arrow crate arrow-flight Changes to the arrow-flight crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants