Repository navigation
ci: proto/ktms/v1 must match KTMS, and internal/gen the copy - #25
Merged
Merged
Conversation
A proto job compares the copy with KTMS at the ref the e2e test uses and regenerates internal/gen, so the console's contract cannot drift from the gateway's unnoticed.
…in run scripts/proto-check.sh clones KTMS at KTMS_REF or the e2e pair, diffs the whole proto/ktms/v1 directory and regenerates internal/gen from scratch, so added or removed files count. The generator plugins are pinned, and the daily main run checks the protocol too.
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
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.
The part of ai-process/docs#68 that needs no BSR: a
protojob diffsproto/ktms/v1/*.protoagainst KTMS atE2E_KTMS_REF(scripts/e2e.refs) and checks thatinternal/genis generated from the copy. KTMS already checks itsusage-proto/copy against light-tokenmeter. Both pass locally.