Skip to content

ci: add command-triggered MCP conformance - #6512

Open
lucarlig wants to merge 11 commits into
chore/mcp-sdk-v2from
user/luca/cf-integration-conformance-ci
Open

ci: add command-triggered MCP conformance#6512
lucarlig wants to merge 11 commits into
chore/mcp-sdk-v2from
user/luca/cf-integration-conformance-ci

Conversation

@lucarlig

@lucarlig lucarlig commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Runs conformance automatically for non-draft PRs targeting chore/mcp-sdk-v2, including when a draft is marked ready for review. Retains /conformance for trusted contributors once this workflow is on the default branch.

Adds make conformance and make conformance-bless using published cf-integration 0.3.3. Selects only the 2025-11-25 and 2026-07-28 client revisions against the built-in gateway, with a dual-era fixture and conformance tooling inside Docker. Removes the 2025-06-18 baselines.

@lucarlig lucarlig changed the title user/luca/cf integration conformance ci ci: add command-triggered MCP conformance Sep 1, 2026
@lucarlig lucarlig mentioned this pull request Sep 2, 2026
14 tasks
@lucarlig
lucarlig force-pushed the user/luca/cf-integration-conformance-ci branch from 197d63b to 9ea1a3c Compare September 9, 2026 08:51
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
@lucarlig
lucarlig changed the base branch from main to chore/mcp-sdk-v2 September 9, 2026 13:19
@lucarlig
lucarlig force-pushed the user/luca/cf-integration-conformance-ci branch from ac70f73 to e7ab268 Compare September 9, 2026 13:58
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>

@madhu-mohan-jaishankar madhu-mohan-jaishankar left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

few questions

  1. what is built-in-data-plane.yml and fixture-direct.yml. both looks like failure findings.
  2. do we need 2025-06-18 at all. isn't 2025-11-25 and 2026-07-28 enough?

@lucarlig

lucarlig commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator Author

2. 2025-06-18

fixture direct is, fixture to fixture direct call, meaning their server and their tests, rest is our gateway in the middle,we need as a baseline to understand what is not our gateway problem but baseline. will remove 2025-06 shouldn't be there.

Signed-off-by: lucarlig <luca.carlig@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants