Bump rain-deploy to 0.1.8: Robinhood Chain (4663) + BNB Smart Chain (56) - #25
Conversation
`LibRainDeploy.supportedNetworks()` gains the two chains at 0.1.8, so the deploy and the inherited liveness test cover them; `[rpc_endpoints]` and `[etherscan]` gain the matching rows. Import prefixes and the lock move with the bump; no contract bytecode changes. The dispatcher's `suite` choice gains the frozen release keys next to the rolling candidates: a newly supported network needs the RELEASED suites (log tables at 0xc51a…, the addresses every consumer pins), and current source has moved since they were cut. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HiqQdxokJ4edjAFyAkN9G3
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (10)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe project updates ChangesRain deploy configuration and release workflows
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The deployment configuration and workflow choices are internally consistent, with no actionable merge-blocking issue identified. 🚥 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 |
rain-deploy 0.1.8 adds Robinhood Chain (4663) and BNB Smart Chain (56) to
LibRainDeploy.supportedNetworks()(rain.deploy#161, released as #162). This bump takes it, adds the two[rpc_endpoints]+[etherscan]rows the inheritedRainDeployVerifySnapshottest requires (Robinhood Chain via its Blockscout; BscScan is Etherscan V2), and moves the import prefixes and lock. No contract bytecode changes.Dispatcher change.
manual-sol-artifactsgains asuiteinput whose options include the frozen release keys (…@0_1_x) next to the rolling candidate. The inherited liveness test requires every released suite on every supported network, and current source has drifted since those releases, so a candidate dispatch would put a new address on the new chains while every consumer pins the released one.Merge gate. CI's liveness test is red until log-tables@0_1_2 then decimal-float@0_1_2 (the DecimalFloat constructor reads the log tables) are dispatched to 4663 and 56 from this branch (the branch carries the new network list;
maindoes not). Sequence: dispatch → re-run CI → merge. The rainlang deploy key is funded on both chains (RAI-2311).Linear: RAI-2291 / RAI-2312.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HiqQdxokJ4edjAFyAkN9G3
Summary by CodeRabbit
New Features
log-tablesanddecimal-floatreleases at versions 0.1.1 and 0.1.2.Maintenance