fix(deps): Rework mypy-protobuf versioning so Renovate won't update the version we use for codegen #1272
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
…e the version we use for codegen
dixonjoel
approved these changes
Dec 9, 2025
Contributor
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.
What does this Pull Request accomplish?
In #1268 I updated the mypy-protobuf version to ">=3.4,<3.7", but I forgot that Renovate's default rangeStrategy will try to update version ranges like this.
Why should this Pull Request be merged?
Set the mypy-protobuf version in parallel with the grpcio-tools version, which is what controls the oldest compatible protobuf version.
What testing has been done?
PR build