Find existing Docker image tags on GHCR for Hyperlane agent, monorepo, or node service images. Use when the user wants to find a recent image, look up an image for a branch or commit, or check what's currently deployed.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Find existing Hyperlane Docker images on GHCR (ghcr.io/hyperlane-xyz/*).
| Image | Contents |
|---|---|
hyperlane-agent | Rust relayer, validator, scraper |
hyperlane-monorepo | Full TS/Solidity monorepo |
hyperlane-node-services | All TS node services (rebalancer, warp-monitor, ccip-server, keyfunder, relayer) |
The hyperlane-node-services image is a unified image. Set SERVICE_NAME env var at runtime to select which service to run.
<7-char-sha>-<YYYYMMDD>-<HHMMSS> (e.g. c558a9f-20260304-105241) — immutable, used in productionmain, my-feature-branch — mutable, overwritten on each buildpr-123 — ephemeral, cleaned up after 1 weekUse the mutable branch tag directly:
ghcr.io/hyperlane-xyz/hyperlane-agent:main
Query the OCI registry API (no auth needed for public images):
TOKEN=$(curl -s "https://ghcr.io/token?service=ghcr.io&scope=repository:hyperlane-xyz/<IMAGE>:pull" | jq -r .token)
curl -s -H "Authorization: Bearer $TOKEN" "https://ghcr.io/v2/hyperlane-xyz/<IMAGE>/tags/list" | jq '.tags'
Replace <IMAGE> with the image name (e.g. hyperlane-agent).
Grep the tag list for a sha prefix:
TOKEN=$(curl -s "https://ghcr.io/token?service=ghcr.io&scope=repository:hyperlane-xyz/<IMAGE>:pull" | jq -r .token)
curl -s -H "Authorization: Bearer $TOKEN" "https://ghcr.io/v2/hyperlane-xyz/<IMAGE>/tags/list" | jq -r '.tags[]' | grep '<SHA_PREFIX>'
Look up the sha from the last successful build:
# Agent builds
gh run list --workflow=rust-docker.yml --branch=main --status=success --limit=1 --json headSha,createdAt --jq '.[0] | "\(.headSha[:7]) built \(.createdAt)"'
# Monorepo builds
gh run list --workflow=monorepo-docker.yml --branch=main --status=success --limit=1 --json headSha,createdAt --jq '.[0] | "\(.headSha[:7]) built \(.createdAt)"'
# Node service builds
gh run list --workflow=node-services-docker.yml --branch=main --status=success --limit=1 --json headSha,createdAt --jq '.[0] | "\(.headSha[:7]) built \(.createdAt)"'
Then match the sha against the GHCR tag list.
grep -E '(tag|Tag)' typescript/infra/config/docker.ts
ghcr.io/hyperlane-xyz/<image>:<tag>./build-docker-image to trigger one./build-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.
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.
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.