-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Dependency upgrades #4700
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
Comments
Note that #4680 would reduce the need for issues like this, as we could regularly bump all versions. It looks like proto-google-common-protos is broken, in that it doesn't include the .proto files any more. We definitely want google-auth-library-credentials bump. It adds JWT caching. It's disappointing we didn't do that earlier. Note that we should actually bump to 0.10.0, not 0.9.1. jsr305 bump seems like it'd be fine. A week or so after 1.14.0 release we can drop support of Java 6 and bump the version of protobuf. We can also bump Guava at the same time. |
@ejona86 Is this the breakage you're referring to? I just saw this at head. If so, I guess that's a separate issue to fix?
|
@carl-mastrangelo looking at #3961 I don't see any critical reasons to block dropping 6. Am I reading right? Could you consider prioritizing that change? It would be nice to drop Java 6 support across the board for Google libraries. (Java 7 too). |
@elharo, no that's not I was referring to. That's a problem with 1) not having protobuf headers available or 2) having too old a version of protobuf. The problem I was talking about would impact running codegen for .proto files that depend on the generated code in proto-google-common-protos, not compiling codegen. @patflynn, right now we're just biding our time for a few more people to notice the announcement of dropping Java 6 support that we're going to include in the release today. But #3961 is really the place for discussion on dropping support of Java 6. #4671 is for dropping Java 7. |
Filed #4715 for the proto issue |
A question about protobuf version - Can grpc-java work with protobuf 3.6.0 currently after overriding dependency? And what is the current plan to officially move to protobuf 3.6.0+? We have a mixed dependency on protobuf and grpc in C++ and Java. Currently we downgrade to protobuf 3.5.1 across the board to generate universal proto C++ files to accommodate grpc-java. |
grpc-java works with 3.6.0. grpc-java should always work with newer minor/patch versions of dependencies... except for Netty (which is why we have grpc-netty-shaded). v1.15.0 dropped Java 6 support, and it didn't have any fallout. So starting in v1.16 we could have upgraded the protobuf dependency fairly safely. We just got side-tracked with other things and didn't. It would be nice to do for v1.17... |
Maybe for 1.19 we can upgrade protobuf? |
Looks like it's done in build.gradle. Think I saw an example file somewhere that still used the old version though. Searching... |
all of these are done except google-auth-library-credentials which should now be bumped to 0.12.0 |
@elharo, it looks like 0.13.0 is out. That's probably what we'd upgrade to. |
0.13.0 is the latest version. This honestly doesn't do much since any user of our auth API will be depending on the library themselves (we only depend on the interface; no implementation). But getting past 0.9.1 may encourage our users to use a newer version with better JWT handling and 0.9.1 was released 10 months ago, so we're overdue for an update. Fixes grpc#4700
0.13.0 is the latest version. This honestly doesn't do much since any user of our auth API will be depending on the library themselves (we only depend on the interface; no implementation). But getting past 0.9.1 may encourage our users to use a newer version with better JWT handling and 0.9.1 was released 10 months ago, so we're overdue for an update. Fixes grpc#4700
0.13.0 is the latest version. This honestly doesn't do much since any user of our auth API will be depending on the library themselves (we only depend on the interface; no implementation). But getting past 0.9.1 may encourage our users to use a newer version with better JWT handling and 0.9.1 was released 10 months ago, so we're overdue for an update. Fixes #4700
In build.gradle
google_api_protos: 'com.google.api.grpc:proto-google-common-protos:1.0.0' --> 1.12.0
com.google.auth:google-auth-library-credentials:0.9.0 to 0.9.1
com.google.code.findbugs:jsr305:3.0.0 to 3.0.2
protobufVersion 3.5.1 --> 3.6.0
There may be others but these are the ones that are conflicting upstream (that is, other versions already being selected) in google-cloud-java
The text was updated successfully, but these errors were encountered: