ci: backport conformance tests from main to v1.x#2068
Merged
felixweinberger merged 1 commit intov1.xfrom Feb 16, 2026
Merged
Conversation
Backport conformance CI pipeline from main branch with v1.x adaptations: - Add v1.x to push/PR branch triggers, add workflow_dispatch - Remove continue-on-error from both jobs - Align server and client conformance package versions to 0.1.13 - Adapt client.py for v1.x API differences (3-tuple transport, RequestContext type, camelCase field names) - Add expected-failures baseline for auth/resource-mismatch (needs RFC 8707 resource validation backport from main) Server conformance: 40/40 passing Client conformance: 262/263 passing (baseline clean)
5ae1efd to
d234633
Compare
9 tasks
pcarleton
approved these changes
Feb 16, 2026
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.
Motivation and Context
The v1.x branch has no conformance testing. This backports the conformance CI pipeline from main so we can validate protocol compliance on the stable release branch, which is required for Tier 1 SDK status.
How Has This Been Tested?
Both test suites run locally:
The single baselined failure (
auth/resource-mismatch) requires backporting RFC 8707 resource validation from main (PR #2010).Breaking Changes
None.
Types of changes
Checklist
Additional context
Changes from main's version:
continue-on-errorremoved (main still has it)client.pyadapted for v1.x API differences (3-tuple transport return,RequestContexttype, camelCase field names)auth/resource-mismatch