Skip to content

rpc_endpoints/etherscan: add ethereum and hyperevm for rain-deploy 0.1.7's network set - #22

Merged
thedavidmeister merged 1 commit into
mainfrom
2026-08-20-rpc-ethereum-hyperevm
Aug 20, 2026
Merged

rpc_endpoints/etherscan: add ethereum and hyperevm for rain-deploy 0.1.7's network set#22
thedavidmeister merged 1 commit into
mainfrom
2026-08-20-rpc-ethereum-hyperevm

Conversation

@thedavidmeister

Copy link
Copy Markdown
Contributor

Deploy run 32394091051 died in forge's simulation pass at invalid rpc url: ethereum — nothing broadcast on any network. The repo pins rain-deploy 0.1.7, whose supportedNetworks() includes ethereum and hyperevm, but [rpc_endpoints]/[etherscan] still carried only the old five networks. Two entries added to each section, mirroring rain.extrospection.deploy exactly (chain = 1/chain = 999 stated where foundry does not resolve the alias). Same gap rain.metadata#139 fixed there.

QA

  • Discriminating tests: n/a - deploy-config-only change (env-var indirection in foundry.toml); the discriminator is the re-dispatched Manual sol artifacts run proceeding past the 'ethereum' simulation step where run 32394091051 failed
  • Mutations applied: n/a - no code; a wrong alias or env name reproduces the observed 'invalid rpc url' failure in the next dispatch, which is the enforcement
  • Oracle: rain.extrospection.deploy's foundry.toml (the org's working seven-network deploy config) and rain-deploy 0.1.7's supportedNetworks(); the failing run's own log pins the missing alias
  • Category check: unblocks the ruled "deploy rain.factory.deploy"; covered: the two missing networks in both sections, the whole gap the failure names

🤖 Generated with Claude Code

…1.7's network set

supportedNetworks() at the pinned rain-deploy 0.1.7 includes ethereum and
hyperevm; deploy run 32394091051 died in simulation at 'invalid rpc url:
ethereum' because the aliases were absent (nothing broadcast). Entries
mirror rain.extrospection.deploy's, chain stated where foundry does not
resolve the alias.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@thedavidmeister, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 77e3587c-f0db-456f-af08-e8776c7cfbe3

📥 Commits

Reviewing files that changed from the base of the PR and between 6158110 and 73e5f1d.

📒 Files selected for processing (1)
  • foundry.toml

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

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

@thedavidmeister
thedavidmeister merged commit e1a7baf into main Aug 20, 2026
5 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.

1 participant