Update 2026-02-25-dev-update-february-2026.md#804
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThe pull request updates the February 2026 development blog post to document HyperIndex v3.0.0 alpha.13 and alpha.14 releases, introducing the new getWhere API, removing Ordered Multichain Mode, and documenting chain info and cursor skill updates with accompanying code examples. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
blog/2026-02-25-dev-update-february-2026.md (1)
5-5:⚠️ Potential issue | 🟡 MinorUpdate the
descriptionfront-matter to reflect alpha.14 additions.The SEO/meta
descriptionon line 5 only covers alpha.13 features. Now that alpha.14 content (getWhere API, removed Ordered Multichain Mode, Cursor/Claude Skills) is included in the post, the description is stale and will misrepresent the post in search results and social previews.✏️ Suggested update
-description: "Envio Developer Update February 2026: HyperIndex v3 alpha.13 with 3x faster backfills, improved RPC support, MegaETH and Sei indexing, new builder series, and Uniswap v4 alert bots." +description: "Envio Developer Update February 2026: HyperIndex v3.0.0 alpha.13 & alpha.14 — new getWhere API, removed Ordered Multichain Mode, Cursor/Claude skills update, 3x faster backfills, MegaETH and Sei indexing, and more."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@blog/2026-02-25-dev-update-february-2026.md` at line 5, Update the front-matter "description" value to mention the alpha.14 additions so the meta/SEO reflects the full post: include references to the getWhere API, removal of Ordered Multichain Mode, and Cursor/Claude Skills alongside the existing alpha.13 highlights (HyperIndex v3 alpha.13, 3x faster backfills, improved RPC support, MegaETH and Sei indexing, new builder series, Uniswap v4 alert bots) by editing the description field in the post's front-matter.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@blog/2026-02-25-dev-update-february-2026.md`:
- Line 31: The phrase "onchain" appears inconsistently with "on-chain" in the
"Ordered Multichain Mode" paragraph; choose one hyphenation and normalize all
occurrences in that section (e.g., change "onchain order" to "on-chain order" or
vice versa) by editing the paragraph containing the "Ordered Multichain Mode"
heading and the sentence that mentions "on-chain order per chain" so both use
the same form.
- Line 38: The phrase "agentic driven development" should be hyphenated as the
compound modifier "agentic-driven" before "development"; update the sentence
that mentions `envio init` so it reads "...to support agentic-driven
development" replacing "agentic driven development" with "agentic-driven
development".
- Around line 25-28: The fenced code block showing the getWhere API diff lacks a
language identifier; update the block that contains "Old:
context.Entity.getWhere.fieldName.eq(value)" / "New: context.Entity.getWhere({
fieldName: { _eq: value } })" by adding the language specifier `diff`
immediately after the opening triple backticks so the snippet renders with
proper syntax highlighting and resolves markdownlint MD040.
- Around line 44-57: The fenced code block containing TypeScript usage (e.g.,
createTestIndexer(), indexer.chainIds, indexer.chains,
indexer.chains[1].ERC20.abi) needs a language identifier for syntax highlighting
and to satisfy markdownlint MD040; change the opening fence from ``` to
```typescript so the snippet is recognized as TypeScript/JavaScript and leave
the rest of the block unchanged.
- Line 12: Update the opening sentence that currently reads "February brings a
couple new HyperIndex V3 alpha release..." to correct grammar: change it to
"February brings a couple of new HyperIndex V3 alpha releases..." (referencing
the phrase containing "HyperIndex v3.0.0 alpha.13 & alpha.14") so it includes
the missing preposition "of" and pluralizes "release" to "releases".
- Around line 28-29: Add a single blank line between the preceding closing code
fence and the heading "### 🔄 Breaking: Removed Ordered Multichain Mode Support"
so the heading is not treated as part of the fenced code block; locate the
closing ``` before that heading and insert one empty line above the "### 🔄
Breaking: Removed Ordered Multichain Mode Support" line.
---
Outside diff comments:
In `@blog/2026-02-25-dev-update-february-2026.md`:
- Line 5: Update the front-matter "description" value to mention the alpha.14
additions so the meta/SEO reflects the full post: include references to the
getWhere API, removal of Ordered Multichain Mode, and Cursor/Claude Skills
alongside the existing alpha.13 highlights (HyperIndex v3 alpha.13, 3x faster
backfills, improved RPC support, MegaETH and Sei indexing, new builder series,
Uniswap v4 alert bots) by editing the description field in the post's
front-matter.
| <!--truncate--> | ||
|
|
||
| February brings a new HyperIndex V3 alpha release along with expanded network support and feature updates. We shipped HyperIndex v3.0.0 alpha.13 with 3x faster historical backfills, support for DESC indices, improved RPC source support, experimental WebSocket support, and a breaking configuration change with `rpc_config` removed in favour of `rpc`. | ||
| February brings a couple new HyperIndex V3 alpha release along with expanded network support and feature updates. We shipped HyperIndex v3.0.0 alpha.13 & alpha.14 with 3x faster historical backfills, support for DESC indices, improved RPC source support, experimental WebSocket support, and a breaking configuration change with `rpc_config` removed in favour of `rpc`, new getWhere API, removed ordered multichain mode support, big Cursor/Claude update and much more! |
There was a problem hiding this comment.
Grammar: "a couple new … release" → "a couple of new … releases"
"A couple new" is missing the preposition "of", and "release" should be plural to agree with "alpha.13 & alpha.14".
✏️ Suggested fix
-February brings a couple new HyperIndex V3 alpha release along with expanded network support and feature updates.
+February brings a couple of new HyperIndex V3 alpha releases along with expanded network support and feature updates.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| February brings a couple new HyperIndex V3 alpha release along with expanded network support and feature updates. We shipped HyperIndex v3.0.0 alpha.13 & alpha.14 with 3x faster historical backfills, support for DESC indices, improved RPC source support, experimental WebSocket support, and a breaking configuration change with `rpc_config` removed in favour of `rpc`, new getWhere API, removed ordered multichain mode support, big Cursor/Claude update and much more! | |
| February brings a couple of new HyperIndex V3 alpha releases along with expanded network support and feature updates. We shipped HyperIndex v3.0.0 alpha.13 & alpha.14 with 3x faster historical backfills, support for DESC indices, improved RPC source support, experimental WebSocket support, and a breaking configuration change with `rpc_config` removed in favour of `rpc`, new getWhere API, removed ordered multichain mode support, big Cursor/Claude update and much more! |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@blog/2026-02-25-dev-update-february-2026.md` at line 12, Update the opening
sentence that currently reads "February brings a couple new HyperIndex V3 alpha
release..." to correct grammar: change it to "February brings a couple of new
HyperIndex V3 alpha releases..." (referencing the phrase containing "HyperIndex
v3.0.0 alpha.13 & alpha.14") so it includes the missing preposition "of" and
pluralizes "release" to "releases".
| ``` | ||
| Old: context.Entity.getWhere.fieldName.eq(value) | ||
| New: context.Entity.getWhere({ fieldName: { _eq: value } }) | ||
| ``` |
There was a problem hiding this comment.
Add a language identifier to the fenced code block.
The code block shows a before/after diff of the getWhere API. Without a language specifier the block renders unstyled and triggers markdownlint MD040. Use diff for proper syntax highlighting.
✏️ Suggested fix
-```
+```diff
Old: context.Entity.getWhere.fieldName.eq(value)
New: context.Entity.getWhere({ fieldName: { _eq: value } })
```🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 25-25: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@blog/2026-02-25-dev-update-february-2026.md` around lines 25 - 28, The fenced
code block showing the getWhere API diff lacks a language identifier; update the
block that contains "Old: context.Entity.getWhere.fieldName.eq(value)" / "New:
context.Entity.getWhere({ fieldName: { _eq: value } })" by adding the language
specifier `diff` immediately after the opening triple backticks so the snippet
renders with proper syntax highlighting and resolves markdownlint MD040.
| ``` | ||
| ### 🔄 Breaking: Removed Ordered Multichain Mode Support |
There was a problem hiding this comment.
Missing blank line between closing code fence and next heading.
Some Markdown renderers (including Docusaurus/MDX) require a blank line between a closing ``` and the following ### heading. Without it, the heading may be parsed as continuation text of the fenced block.
✏️ Suggested fix
New: context.Entity.getWhere({ fieldName: { _eq: value } })🔄 Breaking: Removed Ordered Multichain Mode Support
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
Verify each finding against the current code and only fix it if needed.
In @blog/2026-02-25-dev-update-february-2026.md around lines 28 - 29, Add a
single blank line between the preceding closing code fence and the heading "###
🔄 Breaking: Removed Ordered Multichain Mode Support" so the heading is not
treated as part of the fenced code block; locate the closing ``` before that
heading and insert one empty line above the "### 🔄 Breaking: Removed Ordered
Multichain Mode Support" line.
</details>
<!-- fingerprinting:phantom:triton:churro -->
<!-- This is an auto-generated comment by CodeRabbit -->
| ``` | ||
| ### 🔄 Breaking: Removed Ordered Multichain Mode Support | ||
|
|
||
| Ordered Multichain Mode forced events across all processed chains into global onchain order, causing significant latency and allowing one bad chain to freeze the entire indexing process. |
There was a problem hiding this comment.
Inconsistent hyphenation: "onchain" vs "on-chain".
Line 31 uses "onchain order" (no hyphen) while line 33 uses "on-chain order per chain" (hyphenated). Pick one form and apply it consistently throughout the section.
🧰 Tools
🪛 LanguageTool
[grammar] ~31-~31: Ensure spelling is correct
Context: ...across all processed chains into global onchain order, causing significant latency and ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@blog/2026-02-25-dev-update-february-2026.md` at line 31, The phrase "onchain"
appears inconsistently with "on-chain" in the "Ordered Multichain Mode"
paragraph; choose one hyphenation and normalize all occurrences in that section
(e.g., change "onchain order" to "on-chain order" or vice versa) by editing the
paragraph containing the "Ordered Multichain Mode" heading and the sentence that
mentions "on-chain order per chain" so both use the same form.
|
|
||
| ### 🤖 Big Cursor/Claude Skills Update | ||
|
|
||
| We updated `envio init` to create projects with multiple skills to support agentic driven development. |
There was a problem hiding this comment.
Hyphenate the compound modifier "agentic-driven".
"agentic driven development" should be "agentic-driven development" when used as a compound adjective before a noun.
✏️ Suggested fix
-We updated `envio init` to create projects with multiple skills to support agentic driven development.
+We updated `envio init` to create projects with multiple skills to support agentic-driven development.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| We updated `envio init` to create projects with multiple skills to support agentic driven development. | |
| We updated `envio init` to create projects with multiple skills to support agentic-driven development. |
🧰 Tools
🪛 LanguageTool
[grammar] ~38-~38: Use a hyphen to join words.
Context: ... with multiple skills to support agentic driven development. The LLM landscape c...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@blog/2026-02-25-dev-update-february-2026.md` at line 38, The phrase "agentic
driven development" should be hyphenated as the compound modifier
"agentic-driven" before "development"; update the sentence that mentions `envio
init` so it reads "...to support agentic-driven development" replacing "agentic
driven development" with "agentic-driven development".
| ``` | ||
| const indexer = createTestIndexer(); | ||
|
|
||
| indexer.chainIds | ||
| indexer.chains | ||
|
|
||
| indexer.chains[1].id | ||
| indexer.chains[1].name | ||
| indexer.chains[1].startBlock | ||
| indexer.chains[1].endBlock | ||
|
|
||
| indexer.chains[1].ERC20.abi | ||
| indexer.chains[1].ERC20.addresses // Useful to test dynamic registrations | ||
| ``` |
There was a problem hiding this comment.
Add a language identifier to the fenced code block.
The snippet is TypeScript/JavaScript. Specifying the language enables syntax highlighting and satisfies markdownlint MD040.
✏️ Suggested fix
-```
+```typescript
const indexer = createTestIndexer();
...🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 44-44: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@blog/2026-02-25-dev-update-february-2026.md` around lines 44 - 57, The fenced
code block containing TypeScript usage (e.g., createTestIndexer(),
indexer.chainIds, indexer.chains, indexer.chains[1].ERC20.abi) needs a language
identifier for syntax highlighting and to satisfy markdownlint MD040; change the
opening fence from ``` to ```typescript so the snippet is recognized as
TypeScript/JavaScript and leave the rest of the block unchanged.
2 participants
Summary by CodeRabbit
New Features
Breaking Changes
Documentation