-
Notifications
You must be signed in to change notification settings - Fork 191
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
protobuf 4.21 support #45
Comments
Working on this. Turns out to be a bit annoying because there's a conflict with a json name on a Reference field... but should be able to get a solution out in a week or two. |
copybara-service bot
pushed a commit
that referenced
this issue
Nov 9, 2023
…is is step 1 of resolving #45. PiperOrigin-RevId: 576140989
copybara-service bot
pushed a commit
that referenced
this issue
Nov 10, 2023
…is is step 1 of resolving #45. PiperOrigin-RevId: 576140989
copybara-service bot
pushed a commit
that referenced
this issue
Nov 13, 2023
…is is step 1 of resolving #45. PiperOrigin-RevId: 576140989
copybara-service bot
pushed a commit
that referenced
this issue
Nov 14, 2023
…is is step 1 of resolving #45. PiperOrigin-RevId: 582013548
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we are locked into 3.x with
~=3.13
.If I forcibly install 4.21, I get this:
Would it be possible to regenerate with a newer protoc and allow for protobuf v4 to be used?
Thank you!
The text was updated successfully, but these errors were encountered: