ci: add cross-repo schema parity gate for wasmagent-js and trace-pipeline - #162
Merged
Merged
Conversation
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.
Adds
.github/workflows/schema-parity.ymlthat runs on every PR touchingschemas/.The workflow checks out wasmagent-js and trace-pipeline at their latest main and runs
scripts/check-schema-parity.py, which verifies:$idlocallyschema_versionstring literals in TS/Python code are in the canonical enumThis prevents a recurrence of the v1.11.0 breakage where 8 schema fields drifted between wasmagent-js and trace-pipeline without a gate to catch it.
Closes #161