feat: conformance for two revisions (T3) - #271
Open
sideeffffect wants to merge 1 commit into
Open
sideeffffect wants to merge 1 commit into
sideeffffect wants to merge 1 commit into
Conversation
…ue T8 (softwaremill#246) T3 (softwaremill#241): run client and server conformance at both 2025-11-25 and 2026-07-28 in CI (4 steps). Rename conformance-baseline.yml to conformance-baseline-2025-11-25.yml and add a client section to conformance-baseline-2026-07-28.yml (37 server, 37 client scenarios still failing, all needing later tickets). Both conformance tasks select the per-spec-version baseline from --requirements / --spec-version. Update both conformance READMEs with the two-revision and single-scenario commands. T8 (softwaremill#246): the modern-result envelope, server/discover and -32022 validation landed in softwaremill#260 (already on this base). Remaining server rules (-32602 missing _meta, -32020 header/_meta mismatch, HTTP 400/404 plain-JSON, notifications gating, server-context request facts, the test_missing_capability / test_logging_tool fixtures) are the WIP continuation tracked by this PR. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
sideeffffect
force-pushed
the
feat/t3-t8-conformance
branch
from
September 23, 2026 14:05
b1e9bd3 to
08dfc0f
Compare
sideeffffect
changed the title
This was referenced Sep 23, 2026
sideeffffect
marked this pull request as ready for review
September 23, 2026 21:50
sideeffffect
changed the title
Author
|
Hello @kubinio123 , what do you think of this plan (the whole PR chain) to implement this? |
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.
Follow-up on the merged 2026-07-28 groundwork (#238, #260). T3 only — T6, T7, T5 and T8 are separate stacked PRs on top of this.
T3 — #241: conformance infrastructure for two revisions
2025-11-25and2026-07-28.conformance-baseline.yml→conformance-baseline-2025-11-25.yml; added aclient:section toconformance-baseline-2026-07-28.yml(server + client scenarios still failing, each needing a later ticket).--requirements/--spec-version(also accepting the--requirements=<v>form), falling back to the 2025-11-25 file.Verified locally — all four combos green (each "Baseline check passed").
Closes #241.
Stack (bottom → top, all on
2026-07-28-protocol-support)#271 (T3, this PR) → #273 (T6) → #275 (T7) → #276 (T5) → #274 (T8)
Each PR above reviews its own delta via the compare link in its description.
🤖 Generated with Claude Code