Correct naming of com_github_lyft_protoc_gen_star go_repository#31169
Correct naming of com_github_lyft_protoc_gen_star go_repository#31169htuch merged 2 commits intoenvoyproxy:mainfrom
Conversation
|
Hi @alexbozhenko, welcome and thank you for your contribution. We will try to review your Pull Request as quickly as possible. In the meantime, please take a look at the contribution guidelines if you have not done so already. |
|
CC @envoyproxy/dependency-shepherds: Your approval is needed for changes made to |
e765253 to
22dd6c7
Compare
|
Seems fine, but maybe I'm a bit dense - how does the Bazel internal name matter? |
|
@htuch: we have a setup where we import this repo and use |
htuch
left a comment
There was a problem hiding this comment.
OK, seems harmless and technically right.
|
/retest |
|
@alexbozhenko unfortunately we have just updated our ci framework so |
Commit Message:Correct naming of com_github_lyft_protoc_gen_star go_repository
Additional Description:
Similar to bufbuild/protoc-gen-validate#900
correct naming should include the major version.
https://go.dev/ref/mod#module-path
So go_repository stanza also should include the major version, to distinguish between the different major versions of the module, that can coexist.
After the change, the naming is consistent:
Risk Level: None
Testing: CI passes...?
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]
Signed-off-by: Alex Bozhenko alexbozhenko@gmail.com