-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Update to protobuf v22.0. #180
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.02.28.00.25.39
Not really any point in doing this here until conda-forge/libprotobuf-feedstock#145 goes in. |
But you're welcome to get a head start. |
Ah, thanks @xylar. I wasn't familiar with how this was packaged. Let me know if I can help with anything. |
It looked like @h-vetinari had a pretty hard go at getting rc2 to work here conda-forge/libprotobuf-feedstock#144, seemingly without quite succeeding. I imagine it'll be a little time before we can update. |
See conda-forge/conda-forge-pinning-feedstock#4075. I'm trying to do abseil first, then grpc, then protobuf. Protobuf will be trickier than usual due to an API/ABI break (new major number). The issues in the PR are solvable, but currently lower priority than shepherding the other migrations. Abseil is currently intertwined with re2 and segfaulting on arrow, where I'll likely need some upstream help. Untangling all of this will take some time, I'm afraid. |
Closing in favor of #186. Thanks @h-vetinari for the effort here. |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)Updating to a new version: https://github.com/protocolbuffers/protobuf/releases/tag/v22.0