Skip to content

rainix-sol test workflow: add RPC_URL_HYPEREVM_FORK secret slot - #286

Open
hardyjosh wants to merge 1 commit into
mainfrom
2026-07-24-hyperevm-fork-rpc-test-workflow
Open

rainix-sol test workflow: add RPC_URL_HYPEREVM_FORK secret slot#286
hardyjosh wants to merge 1 commit into
mainfrom
2026-07-24-hyperevm-fork-rpc-test-workflow

Conversation

@hardyjosh

@hardyjosh hardyjosh commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

The manual sol-artifacts workflow gained a HyperEVM RPC slot in #279, but the shared test workflow (rainix-sol.yamlrainix-sol-test.yaml) did not — so callers' HyperEVM fork tests can never see HYPEREVM_RPC_URL in PR CI and stay env-gated.

This declares RPC_URL_HYPEREVM_FORK (optional, like the other fork RPCs) on rainix-sol.yaml, forwards it to the test job, and maps it to HYPEREVM_RPC_URL alongside the other fork RPC env vars. No behaviour change for callers that don't set the secret.

Unblocks S01-Issuer/st0x.deploy HyperEVM fork tests (RAI-1511).

🤖 Generated with Claude Code

https://claude.ai/code/session_01VPs1hCTxusmaSeFKvoc4Kr

Summary by CodeRabbit

  • Chores
    • Added optional HyperEVM fork RPC configuration to automated testing workflows.
    • Supports sourcing the RPC URL from either a configured secret or repository variable.

The manual sol-artifacts workflow already carries a HyperEVM RPC slot;
the shared test workflow did not, so callers' HyperEVM fork tests can
never see HYPEREVM_RPC_URL in CI. Declare the secret on rainix-sol.yaml,
forward it to the test job, and map it to HYPEREVM_RPC_URL alongside the
other fork RPCs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VPs1hCTxusmaSeFKvoc4Kr
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 48f0da5a-11f9-4a8e-bcad-46b596d9f85e

📥 Commits

Reviewing files that changed from the base of the PR and between aa789b9 and 7e8741e.

📒 Files selected for processing (2)
  • .github/workflows/rainix-sol-test.yaml
  • .github/workflows/rainix-sol.yaml

📝 Walkthrough

Walkthrough

The Solidity GitHub Actions workflows now support an optional Hyperevm fork RPC secret, forward it to the test job, and expose it as HYPEREVM_RPC_URL with a repository-variable fallback.

Changes

Hyperevm RPC configuration

Layer / File(s) Summary
Add and propagate Hyperevm RPC secret
.github/workflows/rainix-sol.yaml, .github/workflows/rainix-sol-test.yaml
Both workflows declare the optional RPC_URL_HYPEREVM_FORK secret. The test workflow forwards it to HYPEREVM_RPC_URL, falling back to the repository variable when the secret is unavailable.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

Suggested reviewers: thedavidmeister, claude

🚥 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 matches the main change: adding the RPC_URL_HYPEREVM_FORK secret slot to the rainix-sol test workflow.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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-07-24-hyperevm-fork-rpc-test-workflow

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.

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