Skip to content

docs(stargate): clarify current and historical compatibility - #1985

Open
ayenisholah wants to merge 1 commit into
cosmos:mainfrom
ayenisholah:docs/stargate-compatibility-guidance
Open

ayenisholah wants to merge 1 commit into
cosmos:mainfrom
ayenisholah:docs/stargate-compatibility-guidance

Conversation

@ayenisholah

Copy link
Copy Markdown

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:

  • Cross-checked release statements against CHANGELOG.md and current connectComet/StargateClient implementations.
  • Prettier 3.6.2 check and git diff --check passed.
  • API reference link returns HTTP 200.
  • Documentation only; no runtime changes. The attempted immutable Yarn install could not validate the checkout's LFS-backed cache archives, so no package build/test result is claimed.

@greptile-apps

greptile-apps Bot commented Nov 1, 2026

Copy link
Copy Markdown

This PR does not match any of the 1 configured review trigger rule.

@ayenisholah
ayenisholah force-pushed the docs/stargate-compatibility-guidance branch from e78b4f4 to 4d8d513 Compare November 3, 2026 09:37

This branch has not been deployed

No deployments
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.

1 participant