Downgrade protos to 3.31.1 #1429
Open
+12
−10
Conversation
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
Bencodes
requested review from
ahumesky,
cgruber,
nkoroste and
restingbull
as code owners
restingbull
approved these changes
Dec 15, 2025
Contributor
|
As alternative to bump |
Contributor
|
Ah, I see @nico-semko (the author) commented, but just for context: bazelbuild/rules_android#434 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While building our project internally I hit proto version conflict issues inside of workers. Going to downgrading these proto versions to 3.31.1 so that we are in alignment with the rest of the eco system, mainly:
These recently got upgraded here 09901ce