Skip to content

fix(ci): skip bytecode check on release PRs and add foundry to CLI install#7588

Merged
paulbalaji merged 3 commits intomainfrom
pb/bytecode-check-not-on-release
Dec 10, 2025
Merged

fix(ci): skip bytecode check on release PRs and add foundry to CLI install#7588
paulbalaji merged 3 commits intomainfrom
pb/bytecode-check-not-on-release

Conversation

@paulbalaji
Copy link
Collaborator

@paulbalaji paulbalaji commented Dec 10, 2025

Summary

  • Skip bytecode-analysis workflow when PR source branch is changeset-release/main, since bytecode changes are expected when package versions bump
  • Add setup-foundry step to install-cli action so forge soldeer works on Windows

Fixes the failing release workflow: https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/20102656686/job/57677592215

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Restrict publish-release workflow so releases only run from the main branch.
    • Skip bytecode analysis on automated changeset release branches to reduce noise.
    • Add a preparatory setup step to CI that runs when caching is disabled, improving build/install consistency.

✏️ Tip: You can customize this high-level summary in your review settings.

…stall

- Skip bytecode-analysis workflow when PR source branch is changeset-release/main,
  since bytecode changes are expected when package versions bump
- Add setup-foundry step to install-cli action so forge soldeer works on Windows

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@changeset-bot
Copy link

changeset-bot bot commented Dec 10, 2025

⚠️ No Changeset found

Latest commit: 95c1ef8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 10, 2025

📝 Walkthrough

Walkthrough

Three CI workflows and a composite action were changed: the install-cli action now includes a conditional "Setup Foundry" step when no-cache is enabled; bytecode-analysis PR trigger was guarded to skip a specific changeset branch; release publishing is guarded to run only on main and also added the Foundry setup step.

Changes

Cohort / File(s) Summary
GitHub Actions — bytecode analysis & release
\.github/workflows/bytecode-analysis.yml, \.github/workflows/release.yml
bytecode-analysis.yml: removed unconditional PR branch wildcard and added a guard to skip runs when github.head_ref == 'changeset-release/main'. release.yml: added if: github.ref == 'refs/heads/main' to the publish-release job.
Composite action — install-cli
\.github/actions/install-cli/action.yml, \.github/actions/setup-foundry/*
Inserted a conditional "Setup Foundry" step into the composite action before the yarn-install-build-without-cache step; it runs when inputs.no-cache != 'false' and invokes the local ./.github/actions/setup-foundry action.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verify branch/ref condition expressions in workflow files.
  • Confirm the conditional placement of the Foundry setup step doesn't break the composite action's input expectations or step ordering.

Possibly related PRs

Suggested reviewers

  • ltyu

Poem

In swampy CI, we tidy the strands,
Foundry wakes when no-cache commands,
Releases now mind the mainline gate,
Bytecode skips the changeset crate,
Quiet fixes — pipelines feel great. 🛠️

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The description includes a clear summary and links to the failing workflow, but lacks several template sections like drive-by changes, backward compatibility assessment, and testing details. Consider adding backward compatibility assessment and explicit testing notes to align with the repository template and provide reviewers with complete context.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the two main changes: skipping bytecode checks on release PRs and adding Foundry to the CLI install action.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch pb/bytecode-check-not-on-release

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 31d3787 and 95c1ef8.

📒 Files selected for processing (1)
  • .github/workflows/release.yml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/release.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (57)
  • GitHub Check: cli-evm-e2e-matrix (core-init)
  • GitHub Check: cli-evm-e2e-matrix (warp-apply-simple-updates)
  • GitHub Check: cli-evm-e2e-matrix (warp-apply-rebalancing-config)
  • GitHub Check: cli-evm-e2e-matrix (warp-check-3)
  • GitHub Check: cli-evm-e2e-matrix (warp-read)
  • GitHub Check: cli-evm-e2e-matrix (warp-apply-ownership-updates)
  • GitHub Check: cli-evm-e2e-matrix (warp-init)
  • GitHub Check: cli-evm-e2e-matrix (warp-rebalancer)
  • GitHub Check: cli-evm-e2e-matrix (warp-send)
  • GitHub Check: cli-evm-e2e-matrix (warp-check-4)
  • GitHub Check: cli-evm-e2e-matrix (warp-check-1)
  • GitHub Check: cli-evm-e2e-matrix (warp-apply-hook-updates)
  • GitHub Check: cli-evm-e2e-matrix (warp-deploy-1)
  • GitHub Check: cli-evm-e2e-matrix (warp-bridge-2)
  • GitHub Check: cli-evm-e2e-matrix (core-apply)
  • GitHub Check: cli-evm-e2e-matrix (warp-deploy-2)
  • GitHub Check: cli-evm-e2e-matrix (warp-check-5)
  • GitHub Check: cli-evm-e2e-matrix (warp-check-2)
  • GitHub Check: cli-evm-e2e-matrix (warp-apply-submitters)
  • GitHub Check: cli-evm-e2e-matrix (warp-bridge-1)
  • GitHub Check: cli-evm-e2e-matrix (warp-extend-config)
  • GitHub Check: cli-evm-e2e-matrix (warp-extend-recovery)
  • GitHub Check: cli-evm-e2e-matrix (core-read)
  • GitHub Check: cli-evm-e2e-matrix (warp-extend-basic)
  • GitHub Check: cli-evm-e2e-matrix (relay)
  • GitHub Check: cli-evm-e2e-matrix (warp-apply-ism-updates)
  • GitHub Check: cli-evm-e2e-matrix (core-check)
  • GitHub Check: cli-evm-e2e-matrix (core-deploy)
  • GitHub Check: cli-cosmos-e2e-matrix (core-read)
  • GitHub Check: env-test-matrix (testnet4, sepolia, core)
  • GitHub Check: env-test-matrix (mainnet3, ethereum, igp)
  • GitHub Check: env-test-matrix (mainnet3, optimism, core)
  • GitHub Check: env-test-matrix (mainnet3, optimism, igp)
  • GitHub Check: env-test-matrix (mainnet3, ethereum, core)
  • GitHub Check: env-test-matrix (mainnet3, arbitrum, igp)
  • GitHub Check: cli-cosmos-e2e-matrix (warp-read)
  • GitHub Check: env-test-matrix (mainnet3, arbitrum, core)
  • GitHub Check: cli-cosmos-e2e-matrix (core-check)
  • GitHub Check: cli-cosmos-e2e-matrix (core-apply)
  • GitHub Check: cli-cosmos-e2e-matrix (warp-deploy)
  • GitHub Check: cli-cosmos-e2e-matrix (core-deploy)
  • GitHub Check: cli-radix-e2e-matrix (warp-apply-route-extension)
  • GitHub Check: cosmos-sdk-e2e-run
  • GitHub Check: aleo-sdk-e2e-run
  • GitHub Check: cli-cross-chain-e2e-matrix (warp-apply)
  • GitHub Check: cli-radix-e2e-matrix (warp-apply-ownership-updates)
  • GitHub Check: cli-radix-e2e-matrix (core-deploy)
  • GitHub Check: cli-radix-e2e-matrix (warp-deploy)
  • GitHub Check: cli-cross-chain-e2e-matrix (warp-deploy)
  • GitHub Check: cli-install-test-run
  • GitHub Check: yarn-test-run
  • GitHub Check: infra-test
  • GitHub Check: lint-rs
  • GitHub Check: test-rs
  • GitHub Check: lander-coverage
  • GitHub Check: diff-check
  • GitHub Check: e2e-matrix (evm)

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 and usage tips.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@paulbalaji paulbalaji enabled auto-merge December 10, 2025 15:27
@paulbalaji paulbalaji added this pull request to the merge queue Dec 10, 2025
Merged via the queue into main with commit 5ff589c Dec 10, 2025
85 checks passed
@paulbalaji paulbalaji deleted the pb/bytecode-check-not-on-release branch December 10, 2025 15:46
@github-project-automation github-project-automation bot moved this from In Review to Done in Hyperlane Tasks Dec 10, 2025
@codecov
Copy link

codecov bot commented Dec 10, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (053ec60) to head (95c1ef8).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@     Coverage Diff      @@
##   main   #7588   +/-   ##
============================
============================
Components Coverage Δ
core ∅ <ø> (∅)
hooks ∅ <ø> (∅)
isms ∅ <ø> (∅)
token ∅ <ø> (∅)
middlewares ∅ <ø> (∅)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants