1 Commits (b6fdf2f7feb3622faf7aa9e82e4863debf2bb6f6)

Author	SHA1	Message	Date
Lee	f8b6ea467a	CLI warp route deploys do not support ISM configuration (#3611) ... ### Description This PR fixes multiple related issues (see Related issues). The primary changes are 1) Update the warp-route-deployment.yaml to a more sensible [schema](75d590eff8/typescript/cli/examples/fork/warp-route-deployment.yaml). This schema _sets_ us up to allow multi-chain collateral deployments 2) Use zod to define and validate schemas 3) Removes [intermediary config objects](6c42a6458d/typescript/cli/src/deploy/warp.ts (L176-L214)), and completely rely on warp config file ### Drive-by changes - Updates dry run to allow a user to specify what chain to do a dry run on: `hyperlane deploy warp -d sepolia` ### Related issues - Fixes #3479 - Fixes #3135 - Fixes #3188 ### Backward compatibility **Not backwards compatible, warp route schema has changed** ### Testing Manual - used `sh ci-test.sh pi_with_core_chain` to test out create ERC20, ERC721, CollateralVault, Native warp configs - used `sh ci-test.sh pi_with_core_chain` to test out deploy ERC20, ERC721, CollateralVault, Native warp configs Unit Tests - Unit tests added to test out some business logic related to the schema fields	7 months ago