add(developer-hub): refresh push-feed pro_compatible_status (2026-07-24) - #3930
Open
aditya520 wants to merge 1 commit into
Open
add(developer-hub): refresh push-feed pro_compatible_status (2026-07-24)#3930aditya520 wants to merge 1 commit into
aditya520 wants to merge 1 commit into
Conversation
|
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}
Refresh pro_compatible_status across every Pro-compatible push-feed JSON using a single fetch of https://pyth.dourolabs.app/hermes/v2/price_feeds, and bump the SponsoredFeedsTable "Last refreshed" JSDoc marker to 2026-07-24. Applies the data-source rule uniformly to every feed in every JSON under push-feeds/data/, including the 4 files that previously did not carry the field. 33 status flips (all coming_soon -> available), 57 new pro_compatible_status field additions on those 4 files.
aditya520
force-pushed
the
hydra/i-uxxkgajg/head
branch
from
July 24, 2026 13:20
2533603 to
848f97f
Compare
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.
Summary
Refresh the
pro_compatible_statusfield across every Pro-compatible push-feed docs JSON underapps/developer-hub/content/docs/price-feeds/core/push-feeds/data/, and bump theSponsoredFeedsTableJSDocLast refreshedmarker from2026-07-03to2026-07-24. Every status is recomputed uniformly (Avalanche included) from a single fetch ofhttps://pyth.dourolabs.app/hermes/v2/price_feeds— feeds whose id is present in that listing becomeavailable, all otherscoming_soon.Net effect: 33 status flips (all
coming_soon->available; no reverse flips) on 6 files, plus 57 first-time field additions on the 4 files (aptos-mainnet.json,movement-mainnet.json,svm/fogo-mainnet.json,svm/fogo-testnet.json) that previously did not carrypro_compatible_statusat all. No ids, aliases, thresholds, ordering, or other fields are touched.The
pro_compatible_statustype inSponsoredFeedsTable/index.tsxis already optional (pro_compatible_status?: ProCompatibleStatus), andProCompatibleStatusBadgeis only rendered when the caller opts in viashowProCompatibleStatus— so populating the field on those 4 files is additive to the schema and does not change existing rendering. The developer-hub type-check confirms.Hermes fetch summary
GET https://pyth.dourolabs.app/hermes/v2/price_feeds2026-07-24T13:07:17ZSupersedes
This PR supersedes #3907, which is still open pending human-maintainer approval. #3907's 28 flips are a proper subset of the 33 in this PR (this cycle adds 5 net-new:
RSETH/USD,NAVX/USD,NS/USD,BUCK/USD,CASH/RD.RR), and this PR also carries the same 4-file field-addition set that #3907 introduced. Merging this PR fully subsumes #3907. #3907 can be closed once this lands.Per-file status counts (before/after, format
available/coming_soon)Explicit flip list (33 total, all
coming_soon->available)The list matches the 33 flips called out on the tracking issue exactly.
Additional drift found beyond the parent-issue report
None on any file that already carried
pro_compatible_status. Every file whose parent-issue drift list is empty produced zero status flips, and no file exceeded its reported flip count.First-time
pro_compatible_statusfield additions (57 total, on the 4 files that lacked the field)Per the load-bearing data-source rule ("For every feed in every JSON… set
pro_compatible_statustoavailableif itsidis in that set, otherwisecoming_soon"), the field is now populated on every feed in the 4 previously-unfielded files. This mirrors what the superseded #3907 did.Verification
pnpm turbo run test:format test:types test:lint --filter=@pythnetwork/developer-hub— passed (46 tasks successful).pro_compatible_statusmatchesavailableiff itsidis in the Hermes fetch set; 0 mismatches, 33 net flips + 57 new fields.git merge-tree origin/main HEAD— no conflict output; rebase-clean againstmainat fetch time.pro_compatible_statusstring values changed or added — no id/alias/threshold/order edits) + 1 tsx file (only the JSDocLast refresheddate bump).