docs: correct the deployed hub version on celo-sepolia - #2271
Conversation
The rollout section said celo-sepolia was on 2.12.0. It is on 2.13.0, the same as celo. The error came from reading the wrong half of deployments/registry.json. Its `versions` block records a 2.12.0 deployment for celo-sepolia and a 2.13.0 deployment for celo only, which reads as sepolia being a version behind. The `networks.<net>.deployments` block -- which is what records what is currently deployed -- has celo-sepolia at currentVersion 2.13.0, impl 0x244c93516Abd58E1952452d3D8C4Ce7D454776B8, against proxy 0x16ECBA51e18a4a7e61fdC417f0d47AFEeDfbed74. The two blocks disagree because the sepolia 2.13.0 deployment was never added to the versions history. The section's actual claim is unaffected: no v2.14.0 exists on either chain, so the prover setters and registerProverKey are callable on neither, which is why v2.14.0 has to be deployed before the prover config steps. Only the number was wrong -- but a version number in a deploy runbook is exactly the kind of detail an operator checks against rather than derives, so it is worth being right. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe upgrade guide now lists Celo and Celo Sepolia at version 2.13.0. It continues to state that the v2.14.0 prover-key functions and setters are unavailable on the deployed hubs. ChangesDeployment documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This change corrects a deployed version number in the upgrade guide without changing product behavior or deployment configuration; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
1 participant
The rollout section added in #2267 says celo-sepolia is on 2.12.0. It's on 2.13.0, same as celo.
Where the error came from
deployments/registry.jsonrecords this in two places that disagree:versions.IdentityVerificationHub.*.deploymentsnetworks.<net>.deploymentsThe second is what records what's currently deployed:
The blocks disagree because the sepolia 2.13.0 deploy was never added to the versions history. I read the first one.
What this does and doesn't change
The section's claim is unaffected — no v2.14.0 exists on either chain, so
registerProverKeyand the fourupdateProver…setters are callable on neither, which is exactly why v2.14.0 has to be deployed before the prover-config steps.Only the number was wrong. But a version number in a deploy runbook is something an operator checks against rather than derives, so it's worth being right — an engineer reading "sepolia is on 2.12.0" might reasonably plan two upgrades where one is needed.
Worth a separate look: the
versionsblock is missing the sepolia 2.13.0 entry entirely. Not fixed here since it's generated deployment metadata rather than docs, but it's what made the mistake available to make.🤖 Generated with Claude Code
Summary by CodeRabbit