ci: run cross-SDK conformance corpus on every PR - #15
Merged
Conversation
Adds a conformance job that checks out the pinned conformance suite and runs the Python runner (STC_ONLY=python) against the golden corpus, reding any PR that drifts this SDK's decisions. Needs Node (the orchestrator) and uv (the runner), and the CONFORMANCE_REPO_TOKEN secret (read access to the private conformance repo).
ranael-garem
marked this pull request as ready for review
July 30, 2026 13:42
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 a
conformancejob that guards this SDK against behavioral drift from its sibling SDKs.The job checks out the pinned conformance suite (
getsupertab/connect-sdk-conformanceatv0.3.0) and runs its golden corpus against this repo's Python runner (STC_ONLY=python). Any PR that changes a verify / enforce / customer-match / customer-obtain decision away from the golden value reds the check.main, so a corpus edit can't spontaneously red open SDK PRs — bumping the pin is a deliberate one-line PR here.CONFORMANCE_REPO_TOKENrepo secret (read-only access to the private conformance repo). Skipped on fork PRs, which don't receive the secret.Tier-1 of the two-tier conformance CI; the central all-SDK matrix lives in the conformance repo.
🤖 Generated with Claude Code