Skip to content

Enable gradual migration to protobuf v2 APIs #125

Draft
odsod wants to merge 2 commits intoaep-dev:mainfrom
odsod:initial-v2
Draft

Enable gradual migration to protobuf v2 APIs #125
odsod wants to merge 2 commits intoaep-dev:mainfrom
odsod:initial-v2

Conversation

@odsod
Copy link
Contributor

@odsod odsod commented Feb 8, 2026

First commit backports the v2 linter engine from https://github.com/googleapis/api-linter - intentionally no changes made.

Second commit incorporates the v2 linter engine to run alongside the existing v1 engine. Enabling gradual migration of linter rules from v1 to v2 in subsequent changes.

Trade-off of this approach (running v1 and v2 simultaneously) is increased processing cost from parsing all files twice (jhump/protoreflect and bufbuild/protocompile). Benefit is we can make minimal changes to the existing battle-tested v1 and v2 code during the migration.

odsod and others added 2 commits February 8, 2026 20:08
Heavy lifting for migration to protobuf v2 APIs already done by
@noahdietz and @quirogas - reusing the code as-is.

Kudos.

Co-authored-by: Noah Dietz <noahdietz@users.noreply.github.com>
Co-authored-by: Santiago Quiroga <quirogas@users.noreply.github.com>
Aiming for a surgical change that runs the v1 and v2 linter engines in
parallel during a transitional period where we gradually migrate all the
v1 rules to the v2 APIs.
@toumorokoshi
Copy link
Member

@rambleraptor gentle nudge - can you take a look when you have a chance?

Copy link
Member

@rambleraptor rambleraptor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tests pass and this looks like new code paths. Fine for me!

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.

3 participants

Comments