docs(developer-hub): refresh push-feed pro_compatible_status (2026-07-31) - #3946
docs(developer-hub): refresh push-feed pro_compatible_status (2026-07-31)#3946aditya520 wants to merge 1 commit into
Conversation
…-31) Recompute pro_compatible_status for every feed under apps/developer-hub/content/docs/price-feeds/core/push-feeds/data/ against a fresh Hermes fetch (https://pyth.dourolabs.app/hermes/v2/price_feeds, 1496 unique feed ids as of 2026-07-31T13:11 UTC). 34 flips coming_soon -> available across 6 files; 57 first-time field additions across aptos, movement, and svm/fogo-{mainnet,testnet}. Bump SponsoredFeedsTable JSDoc "Last refreshed" from 2026-07-03 to 2026-07-31.
|
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}
| "confidence_ratio": 100, | ||
| "pro_compatible_status": "available" |
There was a problem hiding this comment.
🔍 Newly added status fields on Aptos/Movement/Fogo are not rendered anywhere
This file (and movement/movement-mainnet.json, svm/fogo-mainnet.json, svm/fogo-testnet.json) now carries pro_compatible_status on every entry, but the pages that consume them do not pass showProCompatibleStatus (content/docs/price-feeds/core/push-feeds/aptos.mdx:18, movement.mdx:18, fogo.mdx:19-23), so the new column is not displayed for these networks. The data is inert until those pages opt in — worth confirming the intent is to pre-populate data rather than also surface the column, since a stale unrendered field can silently drift.
Was this helpful? React with 👍 or 👎 to provide feedback.
| "confidence_ratio": 100, | ||
| "pro_compatible_status": "coming_soon" |
There was a problem hiding this comment.
🔍 Testnet feed ids evaluated against the mainnet Hermes listing
The four Fogo testnet ids are not present in the mainnet Hermes listing (https://pyth.dourolabs.app/hermes/v2/price_feeds), so they are uniformly labelled coming_soon. This is mechanically consistent with the documented derivation rule (apps/developer-hub/src/components/SponsoredFeedsTable/index.tsx:18-28), but the value carries no real signal for a testnet network — if the Fogo page ever enables the column, all four rows would show "Coming soon" regardless of actual Pro availability.
Was this helpful? React with 👍 or 👎 to provide feedback.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4fc3fd3a17
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| * otherwise "coming_soon". | ||
| * | ||
| * Last refreshed 2026-07-03. To refresh, re-run the steps above. | ||
| * Last refreshed 2026-07-31. To refresh, re-run the steps above. |
There was a problem hiding this comment.
Now that this patch adds pro_compatible_status to all 46 Aptos and Movement entries, the refresh instructions still scope the data files to {evm,sui,svm}/*.json. A future maintainer following this recipe can therefore leave Aptos and Movement statuses stale while advancing the refresh date; update the documented path to cover those directories or use a recursive glob for the entire data tree.
Useful? React with 👍 / 👎.
1 participant
Summary
Refresh the
pro_compatible_statusfield on every push-feed docs JSON to reflect live Hermes availability, and bump the SponsoredFeedsTable JSDocLast refresheddate. Recomputed against a fresh Hermes fetch:https://pyth.dourolabs.app/hermes/v2/price_feedsreturned 1496 unique 64-hex feed ids at 2026-07-31T13:11 UTC. Every feed underapps/developer-hub/content/docs/price-feeds/core/push-feeds/data/(all 18 JSONs) is reset toavailableiff itsidis in that set, otherwisecoming_soon— applied uniformly, Avalanche included.Supersedes
This PR supersedes both prior open cycles and both can be closed by the maintainer once this lands:
This cycle's drift set is a strict superset of both prior cycles': the same 34 status flips (identical to #3930's 33 +
INF/SOL.RRonsvm/solana-mainnet.json) plus the same 57 first-time field additions across the same 4 files, all computed fresh fromorigin/mainrather than rebased.Before/after status counts
Per-file counts of
pro_compatible_statusbefore this PR (available/coming_soon/no-field) and after (available/coming_soon):Status flips (34)
All flips are
coming_soon -> available:Additional drift found beyond the parent-issue report
None. The fresh Hermes fetch surfaced the same 34 flips reported in the parent issue and no additional drift.
First-time field additions (57)
Files whose entries previously lacked
pro_compatible_statusnow carry it on every entry, computed from the same Hermes fetch:availablecoming_soonHermes fetch summary
https://pyth.dourolabs.app/hermes/v2/price_feedsOut of scope
No changes to feed ordering, aliases, ids,
time_difference/price_deviation/confidence_ratio, or any component logic. The only edit toSponsoredFeedsTable/index.tsxis theLast refresheddate in the top-of-file JSDoc (line 28:2026-07-03->2026-07-31). The Avalanche_commentcarve-out remains absent onmainand is not reintroduced — Avalanche's status is recomputed data-driven like every other chain.Verification
pnpm turbo run test:format test:types test:lint --filter=@pythnetwork/developer-hub— 46 tasks passed (developer-hub build included).availableor false-negativecoming_soonremaining).