Conversation
stephanos
commented
Oct 2, 2026
| @@ -0,0 +1,5136 @@ | |||
| // Copyright 2023-2026 Buf Technologies, Inc. | |||
Contributor
Author
There was a problem hiding this comment.
Vendored just like the other ones like google/.
3 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
Add standard Buf
requiredannotations to the eight standalone Nexus requests and Start response run ID, vendor the pinned upstream schema, and document its use.Why?
Declare zero/empty-field constraints in the API for automatic validation by consuming applications.
Breaking changes
No protobuf wire changes; enforcing the annotations rejects invalid requests, and optional fields retain their existing contracts.
Server PR
API-Go#320 generates the annotations consumed by Server#12364; merge and publish in API → API-Go → Server order.