hardhat-deploy-migration

To migrate hardhat-deploy from v1 to v2, you must update dependencies, restructure configurations, convert deploy scripts, and update tests. The migration guide provides a step-by-step plan with concrete transformation rules and worked examples to ensure a successful upgrade.

Configuration changes for hardhat-deploy v2 require adjusting your hardhat.config.ts and adding rocketh/config.ts alongside rocketh/deploy.ts. These restructuring steps align your project with the new v2 architecture.

You need to convert deploy scripts for hardhat-deploy v2 when upgrading your deployment tooling to the new architecture. The migration guide provides detailed code transformation rules for converting v1 patterns to v2 equivalents.

To update Ethereum test fixtures for hardhat-deploy v2, apply the detailed code transformation rules provided in the migration guide. The process includes updating test fixtures and environment setup to align with v2 patterns.

The best way to troubleshoot hardhat-deploy migration issues is to follow the guide's migration checklist to verify success across environments. The guide covers troubleshooting steps and points to real-world template repositories for practical reference.