-
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
Update protobuf to 29.3 #25248
base: master
Are you sure you want to change the base?
Update protobuf to 29.3 #25248
Conversation
the test logs are in the "artifacts" tab of the failed test job. Your failure is probably because you need to update the default lockfile ( |
Versions 29.0 and below pollute the default maven repo name with protobuf's dependencies. Update to a version that doesn't.
The change moves some jar artifacts from a repository (maven) to another (protobuf_maven) and there are several errors related to downloading these artifacts. I've noticed that the command that is failing has this flag (which I am unfamiliar with):
I am guessing it's probably related to that. |
Java artifacts used by protobuf are now under repository protobuf_maven instead of maven. Pass along this information.
@@ -202,11 +202,19 @@ write_file( | |||
content = [get_canonical_repo_name("@maven")], | |||
) | |||
|
|||
_PROTOBUF_MAVEN_CANONICAL_REPO_NAME = "rules_jvm_external++maven+protobuf_maven" | |||
|
|||
write_file( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Wyverald I'm not particularly happy with the result, maybe you can advise?
Versions 29.0 and below pollute the default maven repo name with protobuf's dependencies. Update to a version that doesn't.