[stubsabot] Bump protobuf to ~=6.33.5#14887
Conversation
70a50fa to
837eb16
Compare
837eb16 to
fc72b3d
Compare
fc72b3d to
a30ec61
Compare
a30ec61 to
de9c113
Compare
Release: https://pypi.org/pypi/protobuf/6.33.5 Homepage: https://developers.google.com/protocol-buffers/ Repository: https://github.com/protocolbuffers/protobuf Typeshed stubs: https://github.com/python/typeshed/tree/main/stubs/protobuf If stubtest fails for this PR: - Leave this PR open (as a reminder, and to prevent stubsabot from opening another PR) - Fix stubtest failures in another PR, then close this PR Note that you will need to close and re-open the PR in order to trigger CI
de9c113 to
eb4f9b5
Compare
|
@JelleZijlstra or @srittau, sorry for the ping, but I was wondering if we could merge this? This vulnerability requires us to update protobuf at my work, and it would be nice to have the type stubs. CVE-2026-0994. Alternatively: Anything holding this back that I could help with? |
|
Someone needs to go through the diff (protocolbuffers/protobuf@v32.1...v33.5) and see whether there are any relevant changes for the typeshed stubs. We can't just bump the version number. That said, types-protobuf does not depend on protobuf, so it should be possible to install a newer protobuf version alongside the older stubs. |
|
Ah, now I see. I was confused from the existence of the original pr. I think you are correct in that I can use the older version! Sorry for the noise! |
Release: https://pypi.org/pypi/protobuf/6.33.5
Homepage: https://developers.google.com/protocol-buffers/
Repository: https://github.com/protocolbuffers/protobuf
Typeshed stubs: https://github.com/python/typeshed/tree/main/stubs/protobuf
If stubtest fails for this PR:
Note that you will need to close and re-open the PR in order to trigger CI