-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Upgrade protobuf to 3.13.0, part 2/3 #12108
Conversation
This change does the actual upgrade of Protobuf. I'll send a follow-up to remove the now-unused path-file for `3.11.3` when this has landed (and there is no risk of a rollback). Working towards making Bazel compatible with bazelbuild#11694
Sorry, I have no clue why this is not working. I assume you rebased this on top of head? cc @meteorcloudy |
I took a look but couldn't find suspicious change to the CI. |
@philwo fixed CI, so it runs now |
@philwo deployed new CI workers with a non-broken version of the Buildkite agent. I retried the build and expect it to succeed: https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/6945 |
@com_google_protobuf//:protobuf_java no longer contains the java-lite classes to avoid having Protobuf classes in the classpath more than once (which could happen before if a program depends on :protobuf_java and :protobuf_javalite).
CI passes now, so this is ready for review. |
LGTM, I'll import this |
This change does the actual upgrade of Protobuf. I'll send a follow-up to remove the now-unused patch-file for `3.11.3` when this has landed (and there is no risk of a rollback). Working towards making Bazel compatible with bazelbuild#11694 Closes bazelbuild#12108. PiperOrigin-RevId: 332196682
This change does the actual upgrade of Protobuf. I'll send a follow-up to remove the now-unused patch-file for `3.11.3` when this has landed (and there is no risk of a rollback). Working towards making Bazel compatible with bazelbuild#11694 Closes bazelbuild#12108. PiperOrigin-RevId: 332196682
This change does the actual upgrade of Protobuf. I'll send
a follow-up to remove the now-unused patch-file for
3.11.3
when this has landed (and there is no risk of a rollback).
Working towards making Bazel compatible with #11694