Add Ruby SDK Tier 1 assessment to SDK listing - #3248
Open
koic wants to merge 1 commit into
Open
Conversation
Promotes the Ruby SDK from Tier 2 to Tier 1 in the SDK listing for the 2026-07-28 revision and the draft, per the Tier 1 application modelcontextprotocol#3247, which carries the full SEP-1730 evidence and reproduction steps: server conformance 67/67 and client conformance 50/50 across the frozen 2025-11-25 and 2026-07-28 requirement sets, 100% issue triage, no P0s ever filed, stable v1.2.0, a 4-day spec-tracking gap, and all three required policies published. Follows the Tier 2 listing update (modelcontextprotocol#3128) for its application (modelcontextprotocol#3127).
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.
Promotes the Ruby SDK from Tier 2 to Tier 1 in the SDK listing for the 2026-07-28 revision and the draft, per the Tier 1 application #3247, which carries the full SEP-1730 evidence and reproduction steps: server conformance 67/67 and client conformance 50/50 across the frozen 2025-11-25 and 2026-07-28 requirement sets, 100% issue triage, no P0s ever filed, stable v1.2.0, a 4-day spec-tracking gap, and all three required policies published.
cc @modelcontextprotocol/ruby-sdk