Use the published CLI for registry warp checks

Author: paulbalaji

.github/workflows/check-warp-deploy.yaml

@@ -23,6 +23,13 @@ jobs:
           ref: ${{ github.event.pull_request.head.sha }}
           fetch-depth: 0
 
+      - uses: actions/setup-node@v6
+        with:
+          node-version: 22
+
+      - name: Install Hyperlane CLI
+        run: npm i -g @hyperlane-xyz/cli@latest
+
       - name: Determine Base & Head SHA
         id: determine-base-sha
         run: |
@@ -32,6 +39,7 @@ jobs:
       - name: Check Warp Deploy
         env:
           # Only set PR_NUMBER for non-fork PRs (enables PR commenting)
+          HYPERLANE_SKIP_VERSION_CHECK: '1'
           PR_NUMBER: ${{ github.event.pull_request.head.repo.full_name == github.repository && github.event.pull_request.number || '' }}
           GITHUB_TOKEN: ${{ steps.generate-token.outputs.token }}
         run: |

scripts/check-warp-deploy.sh

@@ -46,17 +46,12 @@ EXIT_CODE=0
 for WARP_ROUTE_ID in $WARP_ROUTE_IDS; do
     export WARP_ROUTE_ID
 
-    # Check 1: Registry YAML vs on-chain (uses --forceRegistryConfig to read registry directly)
-    if docker run --rm \
-        -e REGISTRY_COMMIT=$HEAD_COMMIT \
-        -e CI=true \
-        ghcr.io/hyperlane-xyz/hyperlane-monorepo:main \
-        ./node_modules/.bin/tsx \
-        ./typescript/infra/scripts/check/check-deploy.ts \
-        -e mainnet3 \
-        -m warp \
-        --warpRouteId "$WARP_ROUTE_ID" \
-        --forceRegistryConfig; then
+    # Check 1: Registry YAML vs on-chain via published CLI
+    if hyperlane \
+        --registry "$(pwd)" \
+        -y \
+        warp check \
+        --warp-route-id "$WARP_ROUTE_ID"; then
       ONCHAIN_STATUS="✅"
     else
       ONCHAIN_STATUS="❌"