feat(191): allow and recommend use of editions

[odsod]

🍱 Types of changes

What types of changes does your code introduce to AEP? Put an x in the boxes
that apply

• Enhancement
• New proposal
• Migrated from google.aip.dev
• Chore / Quick Fix

---

If/when accepted, I'll follow up with an update to https://github.com/aep-dev/api-linter/blob/main/rules/aep0191/proto_version.go

[toumorokoshi]

That sounds great! Yes, I was referring specifically to proto3. 2025年11月12日(水) 4:38 Oscar Söderlund ***@***.***>:

…

***@***.**** commented on this pull request. ------------------------------ In aep/general/0191/aep.md.j2 <#382 (comment)>: > @@ -6,7 +6,10 @@ read. ## Syntax -APIs defined in protocol buffers **must** use `proto3` syntax. +APIs defined in protocol buffers **must** use `proto3` syntax or one of the I can add another paragraph under the first one saying: When using `proto3` syntax, fields **should** always be marked optional. But I think it's a bit orthogonal to the syntax directive, so maybe better specified somewhere else? — Reply to this email directly, view it on GitHub <#382 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC7QSH23UBPMXHV7BYACKL34MS4PAVCNFSM6AAAAACLUXF4D6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTINJTGIZTAMRXGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>