Update protobuf dependency to use most recent version#202
Merged
tushar-krishna merged 1 commit intomlcommons:mainfrom Sep 24, 2025
Merged
Update protobuf dependency to use most recent version#202tushar-krishna merged 1 commit intomlcommons:mainfrom
tushar-krishna merged 1 commit intomlcommons:mainfrom
Conversation
|
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
tushar-krishna
approved these changes
Sep 24, 2025
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.
Summary
Refer to #195
Update
pyproject.tomlto use most recent protobuf, instead of capping at5.*This has an inherent risk of the bleeding edge protobuf breaking Chakra.
Test Plan
Additional Notes
I still believe the long term solution to this issue is, during
pip install ./pyproject.toml, not to usegrpc_tools.protocthat forces a version update on its own schedule.