Skip to content

[api] Handle previous message deps sync in contrib api#17855

Closed
fishcakez wants to merge 1 commit intoenvoyproxy:mainfrom
fishcakez:rocket-v4-dep
Closed

[api] Handle previous message deps sync in contrib api#17855
fishcakez wants to merge 1 commit intoenvoyproxy:mainfrom
fishcakez:rocket-v4-dep

Conversation

@fishcakez
Copy link
Copy Markdown
Contributor

Commit Message: Handle previous message deps sync in contrib api
Additional Description: Previously did not correctly handle generating the deps for v4alpha protos inside api contrib, which meant that generated build files could be point at incorrect targets. This was first realized in #17796, which had the v4alpha proto point at the non-contrib v3 location.
Risk Level: Low
Testing: Edit api/contrib/envoy/extensions/filters/network/rocketmq_proxy/v4alpha/ and ran proto format sync to update BUILD files, and included in the commit.
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A

Signed-off-by: James Fish <jfish@pinterest.com>
@lizan
Copy link
Copy Markdown
Member

lizan commented Aug 25, 2021

Thanks! Though I plan to land #17842 to remove all v4alpha today so this would be no longer an issue.

@lizan
Copy link
Copy Markdown
Member

lizan commented Aug 25, 2021

Fixed by #17842

@lizan lizan closed this Aug 25, 2021
@fishcakez fishcakez deleted the rocket-v4-dep branch October 15, 2021 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants