Repository navigation
docs(stargate): clarify current and historical compatibility - #1985
Open
ayenisholah wants to merge 1 commit into
Open
ayenisholah wants to merge 1 commit into
ayenisholah wants to merge 1 commit into
Conversation
|
This PR does not match any of the 1 configured review trigger rule. |
ayenisholah
force-pushed
the
docs/stargate-compatibility-guidance
branch
from
November 3, 2026 09:37
e78b4f4 to
4d8d513
Compare
This branch has not been deployed
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.
The Stargate package README presents a compatibility table ending at CosmJS 0.29 as its current support matrix, even though later releases added newer SDK protobuf types and CometBFT clients.
Label the existing table as historical and document the relevant 0.31, 0.32 and 0.37 additions from the changelog. Explain that connection methods require an RPC endpoint, and distinguish RPC compatibility from custom-module support. Add a link to the API reference.
Related to #1799; this addresses the Stargate compatibility section rather than claiming to update every package README.
Validation: