Skip to content

docs: add Envio to the indexer selection list - #2333

Merged
GigaHierz merged 4 commits into
celo-org:mainfrom
Jordy-Baby:add-envio-indexer-selection
Sep 25, 2026
Merged

GigaHierz merged 4 commits into
celo-org:mainfrom
Jordy-Baby:add-envio-indexer-selection

Conversation

@Jordy-Baby

Copy link
Copy Markdown
Contributor

Hey @GigaHierz, thanks for having Envio in the Celo indexer docs. This adds Envio to the "Indexer Selection" list on the scaling your app page, linking to the existing Envio page at /tooling/indexers/envio.

Lmk if you require anything further on our end.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Jordy-Baby
Jordy-Baby requested a review from a team as a code owner September 24, 2026 15:24

@GigaHierz GigaHierz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approving. Small diff, but I did the provider check properly since it is a listing.

Envio is real and shipping: enviodev/hyperindex is at 561 stars with ~171 commits in the last 90 days and a release cut yesterday (v3.13.0); npm envio is at ~58.6k downloads/month, roughly 4.4x year on year.

More to the point, the Celo support is verifiable rather than asserted. Celo mainnet HyperSync is real at source — packages/cli/src/config_parsing/chain_helpers.rs has Celo = 42220 inside the HypersyncChain subenum, so HyperIndex defaults to HyperSync there — and live: GET https://celo.hypersync.xyz/height returns 200.

The link target /tooling/indexers/envio already exists and is already in nav, so this is just making an existing page reachable from the scaling page. The parenthetical is accurate: self-hosting and Envio Cloud are both real options.

Noting for transparency that this is vendor-submitted — that is fine, and the claims hold up, but it is worth having on the record.

Merging this independently of #2334; I have left correction requests on that one.

@GigaHierz

Copy link
Copy Markdown
Contributor

Heads-up: this is approved and merge-ready — it is held by an unrelated CI outage, not by anything in your diff.

npx mintlify resolves the latest dist-tag at run time, and latest is currently 4.2.931, which carries a transitive dependency on @mintlify/auth-edge@0.0.51 — a package that is not on the npm registry:

$ curl -s -o /dev/null -w '%{http_code}' 'https://registry.npmjs.org/@mintlify%2Fauth-edge'
404

So the required check dies during install, before it reads a single file. This is repo-wide right now, not specific to you.

#2335 pins the CLI version and fixes it. I will merge this the moment that lands — nothing needed from you.

@GigaHierz
GigaHierz merged commit 819a55c into celo-org:main Sep 25, 2026
4 checks passed
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