Repository navigation
Deploy network somnia - #1759
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (10)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (5)
WalkthroughThis PR adds Somnia network onboarding: periphery whitelist entries, a gasZip router mapping, and Somnia deployment address mappings for facets and periphery (chainId 5031). ChangesSomnia Network Onboarding
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@script/deploy/_targetState.json`:
- Around line 2443-2466: The somnia target state in _targetState.json is out of
sync with the actual deployed artifact (deployments/somnia.diamond.json):
entries like WhitelistManagerFacet are present in the deployed diamond but
missing from the somnia target set, while GasZipFacet/GasZipPeriphery appear in
_targetState.json but are not in the deployed artifact. Update the somnia target
set in _targetState.json to match the intended production diamond state (add
missing facets such as WhitelistManagerFacet and remove or correct any GasZip*
entries as appropriate) so that the listings align exactly with
deployments/somnia.diamond.json before merging.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 23582d58-9c9a-412a-8381-83f6c5a4a854
📒 Files selected for processing (9)
config/networks.jsonconfig/permit2Proxy.jsonconfig/relay.jsonconfig/stargateV2.jsonconfig/whitelist.jsondeployments/somnia.diamond.jsondeployments/somnia.jsonfoundry.tomlscript/deploy/_targetState.json
…work-somnia-exp-396
- networks.json, gaszip.json, whitelist.json - deployments/somnia.json Co-authored-by: Cursor <cursoragent@cursor.com>
…contracts into deploy-network-somnia-exp-396
Test Coverage ReportLine Coverage: 88.07% (3206 / 3640 lines) |
Which Linear task belongs to this PR?
https://linear.app/lifi-linear/issue/EXSC-232/sc-deploy-sc-core-setup
Why did I implement it this way?
Checklist before requesting a review
Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)