Add Orange network to EVM contract addresses

[devin-ai-integration]

Description

Added Orange network (Avalanche subnet) to the list of supported EVM mainnet networks in the Pyth price feeds documentation. The network recently went to mainnet and the Pyth contract has been deployed at address 0x2880aB155794e7179c9eE2e38200202908C17B43.

Link to Devin run: https://app.devin.ai/sessions/160d24fb139e4e519d404a437f54658e

Requested by: aditya@dourolabs.xyz (aditya@dourolabs.xyz)

Type of Change

• New Page
• Page update/improvement
• Fix typo/grammar
• Restructure/reorganize content
• Update links/references
• Other (please describe):

Areas Affected

• pages/price-feeds/core/contract-addresses/evm.mdx - Added Orange network entry to mainnet EVM networks table

Checklist

• I ran pre-commit run --all-files to check for linting errors
• I have reviewed my changes for clarity and accuracy
• All links are valid and working (verified explorer URL loads correctly)
• Images (if any) are properly formatted and include alt text (N/A)
• Code examples (if any) are complete and functional (N/A)
• Content follows the established style guide
• Changes are properly formatted in Markdown
• Preview renders correctly in development environment (local build passed)

Human Review Checklist

Please verify:

• Contract address 0x2880aB155794e7179c9eE2e38200202908C17B43 is correct for Orange network mainnet
• Explorer URL pattern https://subnets.avax.network/orange/address/... is the correct format for Avalanche subnet explorers
• Orange network doesn't need to be added to other documentation pages (e.g., network counts, other reference sections)
• This is the mainnet deployment (not testnet)

Additional Notes

• Orange is an Avalanche subnet (Chain ID: 1510)
• The entry is alphabetically ordered between "Optimism" and "Plasma"
• Explorer URL verified to load correctly: https://subnets.avax.network/orange/address/0x2880aB155794e7179c9eE2e38200202908C17B43
• CI Status: All critical checks passed (pre-commit ✅, test ✅, Vercel – docs ✅). Note: "Vercel – documentation" check failed but appears to be a stale/misconfigured check from a different Vercel org (pyth-stuff/documentation vs pyth-network/docs)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Nov 21, 2025 3:27pm
documentation	Error			Nov 21, 2025 3:27pm

[devin-ai-integration]

CI Status Update

All critical checks have passed:

• ✅ pre-commit
• ✅ test
• ✅ Vercel – docs (main deployment)

However, the "Vercel – documentation" check is failing. This appears to be a separate Vercel project under pyth-stuff/documentation (different from the main pyth-network/docs deployment which succeeded).

Question for maintainers: Is the "Vercel – documentation" check still required, or is it a legacy/stale check that can be removed or marked as optional?

The code changes are minimal (single line added to a markdown table), the local build passes, and the main Vercel deployment succeeded. The failing check appears to be a CI configuration issue rather than a code problem.