docs(developer-hub): point Lazer SDK links at pyth-lazer-public - #3940
Open
jayantk wants to merge 1 commit into
Open
docs(developer-hub): point Lazer SDK links at pyth-lazer-public#3940jayantk wants to merge 1 commit into
jayantk wants to merge 1 commit into
Conversation
The Lazer JS/Rust SDKs moved out of pyth-crosschain into pyth-network/pyth-lazer-public, leaving the SDK Repository and Rust SDK protocol module links 404ing. Repoint them at the new repo. Also drop the stale cardano-governance branch link for the Cardano contract sources - those contracts are on main now.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
5 Skipped Deployments
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Contributor
🤖 llms.txt Content ReviewAnalyzed documentation changes — no updates to curated content required. Products reviewed:
Files analyzed |
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.
The Lazer JS/Rust SDKs were moved out of
pyth-crosschainintopyth-network/pyth-lazer-public(crosschain commit8ac81e674, plus symlink cleanup infb6c65432). The developer-hub docs still linked at the old in-repo paths, which now 404.Changes
price-feeds/pro/api/websocket.mdxandprice-feeds/pro/api/index.mdx— "SDK Repository" now points atpyth-lazer-public/tree/main/sdk/jsinstead ofpyth-crosschain/tree/main/lazer/sdk/js.price-feeds/pro/faq.mdx— "Rust SDK protocol module" now points atpyth-lazer-public/blob/main/sdk/rust/protocol/src/message.rs.price-feeds/pro/integrate-as-consumer/cardano.mdx— the Cardano contract-sources link pointed at the unmergedmatej/cardano-governancebranch (404, with aTODO: change once merged into main). The contracts are onmainnow, so the link points there and the TODO is gone.Scope check
I link-checked every
github.comURL inapps/developer-hub/{content,src}(129 unique URLs). The remainingpyth-crosschainLazer links all targetlazer/contracts/{evm,sui,iota,cardano}, which did not move and still resolve. Everything else that references the SDK does so by npm package name or docs.rs/crates.io, which are unaffected.Four unrelated 404s turned up in the same sweep and are left alone here (tracked separately): two
pyth-network/perSDK example links,apps/hermes/client/js/src/HermesClient.ts,apps/developer-hub/data/changelog-diffs, andtarget_chains/iota/cli.Verification
pnpm turbo test --filter=@pythnetwork/developer-hub— 47/47 tasks pass (build, types, lint). Each replacement URL was confirmed to return 200 withcurl -L.