docs(push-feeds): refresh pro_compatible_status and drop Avalanche carve-out - #3875
Conversation
…rve-out Re-derives pro_compatible_status against a single fresh fetch of https://pyth.dourolabs.app/hermes/v2/price_feeds (1298 feed ids, fetched 2026-07-03T13:05:48Z). Avalanche is now data-driven along with every other chain — carve-out removed from the SponsoredFeedsTable JSDoc and from data/evm/avalanche-mainnet.json's _comment.
|
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}
| { | ||
| "_comment": "Avalanche feeds are intentionally pinned to pro_compatible_status \"coming_soon\": Pro-compatible push feeds are not deployed for this chain (no deployment-pro-compatible.yaml). Do NOT auto-derive this field from the Hermes listing for this file. See the JSDoc on ProCompatibleStatus in src/components/SponsoredFeedsTable/index.tsx.", | ||
| "feeds": [ | ||
| { | ||
| "alias": "HLP0/USDC.RR", |
There was a problem hiding this comment.
🚩 Avalanche guard rail removed without replacement
The old _comment in avalanche-mainnet.json and step 3 in the JSDoc (SponsoredFeedsTable/index.tsx:27-31 before this PR) served as an explicit warning to future maintainers: "Do NOT auto-derive this field from the Hermes listing for this file." This guard rail existed because Pro-compatible push feeds are reportedly not deployed for Avalanche (no deployment-pro-compatible.yaml). The PR removes both the JSON comment and the JSDoc step, but the Avalanche feed still has "coming_soon". Without the guard rail, a future data refresh could accidentally flip Avalanche to "available" if the feed ID appears in the Hermes listing, even though the chain doesn't support Pro-compatible push feeds. If the underlying deployment situation for Avalanche hasn't changed, consider preserving some form of documentation (e.g. a simpler comment in the JSON or the JSDoc) to prevent accidental promotion.
(Refers to lines 1-12)
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: f28a55375b
ℹ️ 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".
| * `_comment` in data/evm/avalanche-mainnet.json. | ||
| * | ||
| * Last refreshed 2026-06-23. To refresh, re-run the steps above. | ||
| * Last refreshed 2026-07-03. To refresh, re-run the steps above. |
There was a problem hiding this comment.
This refresh note now leaves only the generic Hermes-ID derivation, but Avalanche still has no pro-compatible-production EVM deployment in the repo: the current Avalanche contracts are the legacy entries in contract_manager/src/store/contracts/EvmPriceFeedContracts.json and EvmWormholeContracts.json, while the pro-compatible list starts later without an Avalanche entry. Since evm.mdx renders showProCompatibleStatus for Avalanche, the next refresh that sees HLP0/USDC.RR in Hermes would mark the Avalanche push feed Available even though users have no upgraded Avalanche contract to use; keep the chain-specific carve-out until the deployment exists.
Useful? React with 👍 / 👎.
2 participants
Summary
Refresh
pro_compatible_statusacross the Pro-compatible push-feed docs JSONs by re-deriving each entry against a single fresh Hermes fetch, and drop the Avalanche pinned-to-coming_sooncarve-out so Avalanche is data-driven like every other chain.Related: [[i-ttsthjrp]], [[i-gcyfpicb]].
Hermes fetch summary
https://pyth.dourolabs.app/hermes/v2/price_feeds2026-07-03T13:05:48Z1300entries →1298unique 32-byte lowercase hex ids (used as the truth set for the whole PR — endpoint not re-fetched mid-run)Scope note
pro_compatible_statustoday lives on theevm/*.json,sui/sui-mainnet.json, andsvm/solana-mainnet.jsonfiles (the ones whose MDX pages render<SponsoredFeedsTable ... showProCompatibleStatus />).aptos/aptos-mainnet.json,movement/movement-mainnet.json, andsvm/fogo-{main,test}net.jsondo NOT currently carry the field — their MDX pages render without the Pro-compatible column. This PR touches only files that already opt in, and the SponsoredFeedsTable JSDoc still enumerates{evm,sui,svm}for that reason. Adding the field to the other chains' data files would be a schema-scope change beyond this drift refresh and is not attempted here.Before / after status counts (available / coming_soon)
Flip list
All 10 flips are
coming_soon -> available, matching the parent-issue drift report exactly. No additional drift was surfaced by the fresh fetch.271c64ce…coming_soon -> availablef59ead01…coming_soon -> available271c64ce…coming_soon -> availablef59ead01…coming_soon -> available271c64ce…coming_soon -> available6968a864…coming_soon -> availablee5b274b2…coming_soon -> availableadd6499a…coming_soon -> availablef8d8d6b6…coming_soon -> available675e36f8…coming_soon -> availableAdditional drift found beyond the parent-issue report: none. The parent's 10-flip list is complete.
Avalanche carve-out removal
_commentfield fromdata/evm/avalanche-mainnet.json(per issue scope).Avalanche carve-out) from the JSDoc onProCompatibleStatusinapps/developer-hub/src/components/SponsoredFeedsTable/index.tsx; the general refresh rule (steps 1–2) remains.Last refreshedline to2026-07-03.HLP0/USDC.RR(aa388e24…) is not present in the current Hermes listing, so under the data-driven rule it stayscoming_soon— the visible status is unchanged, but the mechanism producing it is now uniform with every other chain.Verification
pro_compatible_statusand the expected value derived from the Hermes set (in-set ⇒ available,out-of-set ⇒ coming_soon).pnpm turbo run test:format test:lint test:types --filter @pythnetwork/developer-hub— all 46 tasks green (includesbuildvia the task graph →next buildcompiled and pre-rendered 196 pages successfully).Out of scope (not touched)
SponsoredFeedsTablerendering / column logic.time_difference/price_deviation/confidence_ratio/idedits..mdxpages,llms-price-feeds-core.txt,BinaryFormatCards, etc.).