Skip to content

docs: refresh stale docs.pyth.network URLs across TS/JS SDK READMEs#3718

Open
0xghost42 wants to merge 1 commit into
pyth-network:mainfrom
0xghost42:docs/3228-sdk-readme-urls
Open

docs: refresh stale docs.pyth.network URLs across TS/JS SDK READMEs#3718
0xghost42 wants to merge 1 commit into
pyth-network:mainfrom
0xghost42:docs/3228-sdk-readme-urls

Conversation

@0xghost42
Copy link
Copy Markdown

@0xghost42 0xghost42 commented May 19, 2026

Summary

The docs.pyth.network/documentation/pythnet-price-feeds/* URL space has been retired in favour of the price-feeds/core/* layout under the developer-hub app (see apps/developer-hub/content/docs/price-feeds/core/ and apps/developer-hub/src/app/llms-price-feeds-core.txt/route.ts). Most chain SDK READMEs and a couple of the app READMEs still point at the dead URLs, which 404 for any developer who follows them.

Refs #3228, complements #3677 (which only refreshed the Sui-specific links in the main README and price_pusher CLI help text).

URL mapping applied

Old path New path
documentation/pythnet-price-feeds/best-practices price-feeds/core/best-practices
documentation/pythnet-price-feeds/on-demand price-feeds/core/use-real-time-data/pull-integration/<chain>
documentation/pythnet-price-feeds/hermes#public-endpoint(s) price-feeds/core/api-instances-and-providers/hermes#public-endpoints
documentation/pythnet-price-feeds/hermes#hermes-node-providers price-feeds/core/api-instances-and-providers/hermes#node-providers
documentation/pythnet-price-feeds/near price-feeds/core/use-real-time-data/pull-integration/near
documentation/pythnet-price-feeds/sui price-feeds/core/use-real-time-data/pull-integration/sui (and contract-addresses/sui for the iota README's inline code comment that specifically pointed at state/package IDs)

Notes:

  • For chain-specific on-demand mentions I picked the chain-specific pull-integration/<chain> page (rather than the parent use-real-time-data index) because each chain page already has the integration flow + fee guidance the original link was trying to surface.
  • For Hermes anchors: the new page uses ## Node Providers, so the auto-generated slug is #node-providers (no hermes- prefix). Public-endpoint anchor was inconsistent in old READMEs (#public-endpoint vs #public-endpoints) — both are now normalized to #public-endpoints (matching ## Public Endpoints on the new page).
  • apps/price_pusher/README.md had previously been partially updated to price-feeds/api-instances-and-providers/hermes, but that path has since moved under core/; this PR switches it to price-feeds/core/api-instances-and-providers/hermes and adds the missing #public-endpoints anchor for the public-endpoint reference.

Scope

JS/TS SDK READMEs and app READMEs only — keeping this diff documentation-only for a clean review:

  • apps/hermes/client/js/README.md
  • apps/hermes/server/README.md
  • apps/price_pusher/README.md
  • price_service/client/js/README.md
  • target_chains/aptos/sdk/js/README.md
  • target_chains/ethereum/sdk/solidity/README.md
  • target_chains/ethereum/sdk/stylus/README.md
  • target_chains/fuel/sdk/js/README.md
  • target_chains/near/README.md
  • target_chains/starknet/sdk/js/README.md
  • target_chains/sui/README.md
  • target_chains/sui/sdk/js-iota/README.md
  • target_chains/sui/sdk/js/README.md

The on-chain contract NatSpec / Move doc-comments / Rust doc-comments contain the same stale paths (Solidity IPyth.sol/PythStructs.sol, Sui/Aptos pyth.move/price.move, NEAR receiver/src/{lib,state}.rs, CosmWasm cw-contract/src/contract.rs) and will be refreshed in a follow-up PR so this diff stays JS-only and the on-chain churn can be reviewed against its own consumers.

Test plan

  • grep -rn "documentation/pythnet-price-feeds" --include="*.md" returns no remaining matches in the touched scope
  • Every new URL verified to exist as an .mdx page under apps/developer-hub/content/docs/price-feeds/core/
  • Anchor slugs cross-checked against the headings in apps/developer-hub/content/docs/price-feeds/core/api-instances-and-providers/hermes.mdx
  • Maintainer spot-check that the chain-specific pull-integration/<chain> page is the preferred landing target over the parent use-real-time-data index for "on-demand"-style references

Open in Devin Review

The `docs.pyth.network/documentation/pythnet-price-feeds/*` URL space has
been retired in favour of the `price-feeds/core/*` layout under the
developer-hub app (see e.g. apps/developer-hub/src/app/llms-price-feeds-core.txt
and apps/developer-hub/content/docs/price-feeds/core/). Most chain SDK
READMEs and a couple of the app READMEs still point at the dead URLs,
which 404 for any developer who follows them.

URL mapping applied:
  - documentation/pythnet-price-feeds/best-practices ->
    price-feeds/core/best-practices
  - documentation/pythnet-price-feeds/on-demand ->
    price-feeds/core/use-real-time-data/pull-integration/<chain>
    (chain-specific page where the integration flow lives)
  - documentation/pythnet-price-feeds/hermes#public-endpoint(s) ->
    price-feeds/core/api-instances-and-providers/hermes#public-endpoints
  - documentation/pythnet-price-feeds/hermes#hermes-node-providers ->
    price-feeds/core/api-instances-and-providers/hermes#node-providers
    (the new page uses `## Node Providers`, so the anchor slug is
    `#node-providers`)
  - documentation/pythnet-price-feeds/near ->
    price-feeds/core/use-real-time-data/pull-integration/near
  - documentation/pythnet-price-feeds/sui ->
    price-feeds/core/use-real-time-data/pull-integration/sui
    (the iota README's inline code comment was already specifically
    pointing readers at the Sui state/package IDs, so it now points
    at contract-addresses/sui)
  - apps/price_pusher/README.md was already partially updated to
    `price-feeds/api-instances-and-providers/hermes`, but that path
    has been moved under `core/` since; switched to the new canonical
    `price-feeds/core/api-instances-and-providers/hermes` and added
    the missing `#public-endpoints` anchor

Refs pyth-network#3228, complements pyth-network#3677 (which only refreshed the Sui-specific
links in the main README and price_pusher CLI help text).

On-chain contract NatSpec / Move / Rust doc-comments contain the same
stale paths and will be refreshed in a follow-up PR to keep this diff
JS-only.
@vercel
Copy link
Copy Markdown

vercel Bot commented May 19, 2026

@0xghost42 is attempting to deploy a commit to the Pyth Network Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

View 1 additional finding in Devin Review.

Open in Devin Review

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚩 Old documentation URLs remain in non-Markdown source files

Several source code files still contain old docs.pyth.network/documentation/pythnet-price-feeds/ URLs that were not updated by this PR: apps/price_pusher/src/sui/command.ts, target_chains/cosmwasm/examples/cw-contract/src/contract.rs, target_chains/ethereum/sdk/solidity/PythStructs.sol, target_chains/ethereum/sdk/solidity/IPyth.sol, target_chains/aptos/contracts/Move.toml, target_chains/near/receiver/src/lib.rs, and target_chains/near/receiver/src/state.rs. These are in code comments rather than README files, so they may be intentionally out of scope for this PR, but they should be updated in a follow-up to avoid stale documentation references.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

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