Bump rain-deploy to 0.1.8: Robinhood Chain (4663) + BNB Smart Chain (56)

[hardyjosh]

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 inherited RainDeployVerifySnapshot test requires (Robinhood Chain via its Blockscout; BscScan is Etherscan V2), and moves the import prefixes and lock. rainlang 0.2.1's committed test abstract still imports the rain-deploy-0.1.7/ prefix, so it is aliased onto 0.1.8 in foundry.toml, test-only. No contract bytecode changes.

This repo has no frozen releases yet, so its liveness test has nothing to require on the new chains and CI should be green as-is; the interpreter suite ships to 4663 and 56 as the rolling candidates via the existing dispatcher after merge.

Linear: RAI-2291 / RAI-2312.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HiqQdxokJ4edjAFyAkN9G3

Summary by CodeRabbit

• Chores

  • Updated deployment tooling to the latest supported deployment package version.
  • Improved compatibility with the current Rainlang deployment test and verification workflows.

• New Features

  • Added RPC and contract verification configuration for Robinhood Chain and BNB Smart Chain.
  • Enabled contract verification through the configured verification services for both networks.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 3e339aee-664e-4a08-9825-69256f6789d9

📥 Commits

Reviewing files that changed from the base of the PR and between ad8273c and 4fe4cad.

⛔ Files ignored due to path filters (1)

• soldeer.lock is excluded by !**/*.lock

📒 Files selected for processing (6)

• foundry.toml
• script/Build.sol
• script/Deploy.sol
• src/abstract/RainDeploySuitesBase.sol
• test/src/abstract/RainlangDeployChain.t.sol
• test/src/abstract/RainlangDeploySnapshot.t.sol

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The project upgrades rain-deploy from 0.1.7 to 0.1.8, updates related imports, adds a compatibility remapping for a test import, and configures Robinhood and BSC RPC and verification endpoints.

Changes

Rain Deploy Upgrade

Layer / File(s)	Summary
Dependency and import alignment foundry.toml, script/Build.sol, script/Deploy.sol, src/abstract/RainDeploySuitesBase.sol, test/src/abstract/*	The project uses rain-deploy 0.1.8 across dependency configuration, scripts, source exports, and tests. A remapping resolves the committed legacy test import.
Network and verification configuration foundry.toml	Foundry adds Robinhood and BSC RPC aliases and Etherscan-compatible verification entries. Robinhood uses the Blockscout API endpoint and chain ID 4663. BSC uses chain ID 56.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 4fe4c

This change aligns rain-deploy imports and adds Robinhood and BSC deployment configuration without changing contract bytecode. No merge-blocking correctness or operational risk is evidenced.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main changes: upgrading rain-deploy to 0.1.8 and adding Robinhood Chain and BNB Smart Chain support.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-09-10-rain-deploy-0-1-8

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment