-
Notifications
You must be signed in to change notification settings - Fork 6
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
Bump protobuf
and grpcio
dependencies
#261
Conversation
Signed-off-by: Leandro Lucarella <[email protected]>
This is technically a breaking change, so we might want to wait to merge it if there are any planned fix releases for v0.17.x. |
The `protobuf` version 4.25.x will go out of support soon(ish), on 31 Mar 2025. Since we don't need to keep compatibility to any legacy code, we can bump it in advance as a preparation. The `googleapis-common-protos` version was also bumped to 1.65.0, as the previous version was too old to work with the new `protobuf` version. https://protobuf.dev/support/version-support/#python Signed-off-by: Leandro Lucarella <[email protected]>
1c7d103
to
4869626
Compare
@tiyash-basu-frequenz does the approval means it is ok to merge now? |
Yep, it's ok to merge it, since it does not touch proto files. |
But Python-wise is technically a breaking change, so it shouldn't be released as v0.17.x. This is where having binding and spec files start to get really messy 😬 I guess since we are in pre-1.0 and it is a minor breaking change (you just need to bump deps) it might be OK to make an exception and release in v0.17.x if needed too. |
The
protobuf
version 4.25.x will go out of support soon(ish), on 31 Mar 2025. Since we don't need to keep compatibility to any legacy code, we can bump it in advance as a preparation.The
googleapis-common-protos
version was also bumped to 1.65.0, as the previous version was too old to work with the newprotobuf
version.https://protobuf.dev/support/version-support/#python