feat: add --expected-failures baseline and composite GitHub Action#113
Merged
feat: add --expected-failures baseline and composite GitHub Action#113
Conversation
Add support for SDKs that don't yet pass all conformance tests to still run conformance in CI without failing, by specifying a YAML baseline file of known/expected failures. CLI changes: - Add --expected-failures <path> flag to both server and client commands - Exit 0 if only expected failures occur - Exit 1 if unexpected failures occur (regression) - Exit 1 if an expected failure now passes (stale baseline, must update) GitHub Action (action.yml): - Composite action that builds from source and runs conformance tests - SDKs reference it as: uses: modelcontextprotocol/conformance@<ref> - Inputs: mode, url, command, expected-failures, suite, scenario, etc. New files: - src/expected-failures.ts: YAML loading, baseline evaluation, reporting - src/expected-failures.test.ts: 16 unit tests - action.yml: composite GitHub Action Closes #99
maxisbey
force-pushed
the
expected-failures
branch
from
a7a585f to
4a42c25
Compare
commit: |
This was referenced Jan 21, 2026
pcarleton
approved these changes
Jan 22, 2026
Member
|
Awesome, thanks - will give it a try later 🙏 |
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
3 participants
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.
Summary
Adds support for SDKs that don't yet pass all conformance tests to still run conformance in CI without failing, by specifying a YAML baseline file of known/expected failures.
Closes #99
Changes
--expected-failures <path>CLI flagAdded to both
serverandclientcommands. Points to a YAML file:Exit code logic:
Composite GitHub Action (
action.yml)SDKs can now reference the action directly instead of writing their own npx scripts:
Inputs:
mode,url,command,expected-failures,suite,scenario,timeout,verbose,version,node-versionFiles
src/expected-failures.ts— YAML loading, baseline evaluation, result printingsrc/expected-failures.test.ts— 16 unit testsaction.yml— composite GitHub Actionsrc/index.ts— added--expected-failuresoption to both commandspackage.json— addedyamldependency