Trigger Docker image builds for Hyperlane agent, monorepo, or node service images. Use when the user wants to build new Docker images for a branch, commit, or tag.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Build and publish Docker images to GHCR (ghcr.io/hyperlane-xyz/*).
| Workflow | Image(s) | Contents |
|---|---|---|
rust-docker.yml | hyperlane-agent | Rust relayer, validator, scraper |
monorepo-docker.yml | hyperlane-monorepo | Full TS/Solidity monorepo |
node-services-docker.yml | hyperlane-node-services | All TS node services (rebalancer, warp-monitor, ccip-server, keyfunder, relayer) |
Use gh workflow run with --ref to specify the branch, tag, or commit:
# Agent image (Rust)
gh workflow run rust-docker.yml --ref <branch>
# Monorepo image
gh workflow run monorepo-docker.yml --ref <branch>
# Node services (single unified image)
gh workflow run node-services-docker.yml --ref <branch>
# Include arm64 (multi-arch, slower)
gh workflow run rust-docker.yml --ref <branch> -f include_arm64=true
--ref defaults to main if omitted.
Get the run URL:
gh run list --workflow=<workflow>.yml --limit=1 --json url --jq '.[].url'
Get the run ID (wait a few seconds after triggering for the run to appear):
gh run list --workflow=<workflow>.yml --limit=1 --json databaseId,status,createdAt --jq '.[0]'
Watch it:
gh run watch <run-id>
The resulting image tag will be <7-char-sha>-<YYYYMMDD>-<HHMMSS>, e.g. c558a9f-20260304-105241.
Images are at ghcr.io/hyperlane-xyz/<image-name>:<tag>.
main).gh workflow run.gh run list./find-docker-image skill.docs/docker-image-policy.md for the full Docker image policy.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write a changeset file in the `hyperlane-registry` repo for a PR that adds, updates, or modifies warp route config / chain metadata / addresses. Canonical pattern — never run the interactive `pnpm changeset` CLI; write the file directly. Referenced by any skill that opens a registry PR.
The English summary is being prepared. Showing the original description.
The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.
The English summary is being prepared. Showing the original description.
Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.
The English summary is being prepared. Showing the original description.
Debug why a Hyperlane message is not being processed. Use when given a message ID or explorer URL to investigate delivery failures, gas estimation errors, validator issues, or other processing problems.
The English summary is being prepared. Showing the original description.
Debug RPC provider health issues for a chain. Use when alerts mention RPC failures, high latency, stale blocks, or provider errors. Diagnoses the issue and recommends fixes.
The English summary is being prepared. Showing the original description.
Debug validator checkpoint inconsistencies where some validators are behind others. Use when alerts mention "checkpoint inconsistency", "validators behind", or "inconsistent latest checkpoints", or when asked to debug validator sets, investigate validator delays, or troubleshoot metadata fetch failures for a chain. Defaults to default_ism app context if not specified.
The English summary is being prepared. Showing the original description.