Skip to content

V3 migration guide#763

Merged
DZakh merged 1 commit intomainfrom
dz/v3-migration-guide
Dec 18, 2025
Merged

V3 migration guide#763
DZakh merged 1 commit intomainfrom
dz/v3-migration-guide

Conversation

@DZakh
Copy link
Member

@DZakh DZakh commented Dec 18, 2025

Summary by CodeRabbit

  • Documentation
    • Added comprehensive V3 Alpha migration guide with breaking changes, step-by-step migration steps, and quick checklist.
    • Updated Solana documentation with operational requirements and latency details.
    • Expanded supported networks tables for HyperRPC and HyperSync with additional network entries.
    • Updated navigation to reflect new migration resources.

✏️ Tip: You can customize this high-level summary in your review settings.

@vercel
Copy link

vercel bot commented Dec 18, 2025

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

Project Deployment Review Updated (UTC)
envio-docs Ready Ready Preview, Comment Dec 18, 2025 10:05am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 18, 2025

Walkthrough

This PR adds and updates documentation files for HyperIndex V3 Alpha migration, Solana RPC support operational details, and network support tables for HyperRPC and HyperSync. It also updates sidebar navigation to include the new migration guide. No functional code changes are introduced.

Changes

Cohort / File(s) Summary
HyperIndex Migration Documentation
docs/HyperIndex/migrate-to-v3.md
New comprehensive migration guide for HyperIndex V3 Alpha, including alpha caveats, CommonJS→ESM transition, automatic handler registration, RPC live indexing, chain context, ClickHouse sink, HyperSync latency improvements, Solana support, pnpx init improvements, Block Handler Only Indexers option, flexible entity fields, and preload optimization
HyperIndex Solana Documentation
docs/HyperIndex/solana/solana.md
Updated Notes section with operational details: RPC-only data source, onBlock handler only, block data not fetched automatically, finalized-block tracking with no reorg support, and ~20s latency
Network Support Tables
docs/HyperRPC/hyperrpc-supported-networks.md, docs/HyperSync/hypersync-supported-networks.md
Expanded network support documentation with complete table headers (Network Name, Network ID, URL, Tier) and populated network entries
Sidebar Navigation Configuration
sidebarsHyperIndex.js
Added "migrate-to-v3" item to the Migrate to Envio category in the sidebar items array

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

  • Sidebar change is a straightforward array entry addition
  • Network tables are data/content additions with consistent formatting
  • Migration guide documentation is standard content writing with no logic review needed
  • Verify consistency of table formatting across supported-networks files and accuracy of network entries

Possibly related PRs

Suggested reviewers

  • DenhamPreen
  • JasoonS

Poem

🐰 New docs hop into view, migrations smooth as clover,
Networks tabulated true, from Ab to chains all over,
Solana notes for clarity, sidebar routes renewed,
V3 Alpha's journey mapped—let the indexing move! 🌟

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title directly and clearly describes the main change: adding comprehensive V3 migration documentation including migration steps, breaking changes, and a step-by-step guide.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch dz/v3-migration-guide

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (1)
docs/HyperIndex/migrate-to-v3.md (1)

58-58: Optional: Consider simpler phrasing.

The phrase "remove all of the paths" could be simplified to "remove all the paths" for brevity.

🔎 View suggested fix
-Previously, you needed to specify an explicit path to a handler file for every contract in `config.yaml`. Now you can remove all of the paths from `config.yaml` and simply move the files to `src/handlers`. You can name the files however you want, but we suggest using contract names and having a file per contract.
+Previously, you needed to specify an explicit path to a handler file for every contract in `config.yaml`. Now you can remove all the paths from `config.yaml` and simply move the files to `src/handlers`. You can name the files however you want, but we suggest using contract names and having a file per contract.

Based on static analysis hint.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1f508d5 and 56d726f.

📒 Files selected for processing (5)
  • docs/HyperIndex/migrate-to-v3.md (1 hunks)
  • docs/HyperIndex/solana/solana.md (1 hunks)
  • docs/HyperRPC/hyperrpc-supported-networks.md (1 hunks)
  • docs/HyperSync/hypersync-supported-networks.md (1 hunks)
  • sidebarsHyperIndex.js (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-29T14:30:03.677Z
Learnt from: DenhamPreen
Repo: enviodev/docs PR: 673
File: docs/HyperIndex/supported-networks/chainweb-testnet-21.md:14-16
Timestamp: 2025-07-29T14:30:03.677Z
Learning: Chainweb Testnet 20 (ID: 5920) and Chainweb Testnet 21 (ID: 5921) have non-functional HyperSync endpoints that return HTTP 404, indicating these networks are not properly supported and should be removed from documentation.

Applied to files:

  • docs/HyperRPC/hyperrpc-supported-networks.md
🪛 LanguageTool
docs/HyperIndex/migrate-to-v3.md

[style] ~58-~58: Consider removing “of” to be more concise
Context: ...ct in config.yaml. Now you can remove all of the paths from config.yaml and simply mov...

(ALL_OF_THE)


[grammar] ~441-~441: Ensure spelling is correct
Context: ...nt coming soon) Verify: - [ ] Run pnpm envio codegen and pnpm dev to verify ## G...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (11)
docs/HyperSync/hypersync-supported-networks.md (1)

46-48: LGTM - Formatting improvement.

The additional spacing before the networks table improves readability.

docs/HyperIndex/solana/solana.md (1)

26-29: LGTM - Clear operational constraints documented.

The notes effectively communicate Solana support limitations, including RPC-only source, handler restrictions, manual block fetching requirements, and the ~20s latency from finalized-block tracking.

docs/HyperRPC/hyperrpc-supported-networks.md (1)

38-40: LGTM - Formatting improvement.

The additional spacing before the networks table improves readability.

sidebarsHyperIndex.js (1)

48-48: LGTM - Navigation properly configured.

The new sidebar item correctly references the migration guide document ID.

docs/HyperIndex/migrate-to-v3.md (7)

1-11: LGTM - Frontmatter and alpha warning are clear.

The metadata is properly structured, and the alpha warning appropriately sets expectations.


13-18: LGTM - Clear introduction establishing context.

The introduction effectively communicates the stability of V2 and positions V3 as a modernization effort.


19-146: LGTM - Comprehensive feature documentation.

The new features are well-documented with clear examples and appropriate warnings where needed (e.g., ClickHouse Sink experimental status).


147-184: LGTM - Breaking changes clearly documented.

The breaking changes are well-organized by category with specific details on what changed, making it easy for users to identify required updates.


185-398: LGTM - Excellent step-by-step migration guide.

The migration guide is comprehensive and well-structured. The recommendation to prepare on V2 first (Step 0) is particularly valuable for reducing migration risk.


399-442: LGTM - Helpful migration checklist.

The quick migration checklist provides an excellent summary for users to track their progress through the migration steps.


443-454: Verify external links are accessible.

The ENVIO community exists on Discord, and the HyperIndex GitHub releases page is accessible. However, confirm that all referenced release links (v3.0.0-alpha.0 through alpha.3) are live and that the Discord invite https://discord.gg/envio is properly configured and accepting new members.

pnpx envio@3.0.0-alpha.3 init solana
```

See the [Solana documentation](/docs/HyperIndex/solana) for more details.
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check if the Solana documentation file exists at the expected location
fd -t f "solana.md" docs/HyperIndex/
# Also check what files exist in the docs/HyperIndex directory
echo "---"
echo "Files in docs/HyperIndex/:"
ls -la docs/HyperIndex/

Repository: enviodev/docs

Length of output: 1475


🏁 Script executed:

#!/bin/bash
# Check the contents of the solana directory
echo "Contents of docs/HyperIndex/solana/:"
ls -la docs/HyperIndex/solana/
echo "---"
# Check the migrate-to-v3.md file around line 123 to see the actual link
echo "Context around line 123 in migrate-to-v3.md:"
sed -n '120,130p' docs/HyperIndex/migrate-to-v3.md

Repository: enviodev/docs

Length of output: 687


Fix the Solana documentation link path.

The file exists at docs/HyperIndex/solana/solana.md, but the link points to /docs/HyperIndex/solana (a directory). Update the link to /docs/HyperIndex/solana/solana to reference the actual file.

🤖 Prompt for AI Agents
In docs/HyperIndex/migrate-to-v3.md around line 123, the Solana link points to
the directory /docs/HyperIndex/solana instead of the actual file; update the
markdown link target to /docs/HyperIndex/solana/solana so it references
docs/HyperIndex/solana/solana.md (keep the display text unchanged).

preload_handlers: true
```

2. **If you were using loaders**, migrate them to Preload Optimization following the [Migrating from Loaders](/docs/HyperIndex/preload-optimization#migrating-from-loaders) guide.
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

Correct the Preload Optimization migration guide link.

The link /docs/HyperIndex/preload-optimization#migrating-from-loaders is incorrect. The "Migrating from Loaders" section is on the Event Handlers documentation page. Update the link to /docs/HyperIndex/event-handlers#migrating-from-loaders.

🤖 Prompt for AI Agents
In docs/HyperIndex/migrate-to-v3.md around line 198, the link currently points
to /docs/HyperIndex/preload-optimization#migrating-from-loaders but the
"Migrating from Loaders" section actually lives on the Event Handlers page;
update the link target to /docs/HyperIndex/event-handlers#migrating-from-loaders
so the anchor directs users to the correct documentation section.

@DZakh DZakh requested a review from moose-code December 18, 2025 10:26
Copy link
Member

@moose-code moose-code left a comment

Choose a reason for hiding this comment

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

Amazing, just read through it - looks perfect.

@DZakh DZakh merged commit 4861df3 into main Dec 18, 2025
3 checks passed
@DZakh DZakh deleted the dz/v3-migration-guide branch December 18, 2025 12:31
@coderabbitai coderabbitai bot mentioned this pull request Dec 19, 2025
@DenhamPreen DenhamPreen mentioned this pull request Mar 9, 2026
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.

2 participants