remove pallet xcm migration

Makefile

@@ -32,7 +32,8 @@ format:
 
 .PHONY: try-runtime
 try-runtime:
-	try-runtime --runtime ./target/release/wbuild/hydradx-runtime/hydradx_runtime.wasm on-runtime-upgrade --checks all live --uri --uri wss://rpc.hydradx.cloud:443
+	cargo build --release --features try-runtime
+	try-runtime --runtime ./target/release/wbuild/hydradx-runtime/hydradx_runtime.wasm on-runtime-upgrade --checks all live --uri wss://rpc.hydradx.cloud:443
 
 .PHONY: build-docs
 build-docs:

README.md

@@ -179,7 +179,7 @@ The `try-runtime` tool can be used to test storage migrations and runtime upgrad
 Run the following command to test against the state on HydraDX.
 Don't forget to use a runtime built with `try-runtime` feature.
 ```bash
-try-runtime --runtime ./target/release/wbuild/hydradx-runtime/hydradx_runtime.wasm on-runtime-upgrade --checks all live --uri --uri wss://rpc.hydradx.cloud:443
+try-runtime --runtime ./target/release/wbuild/hydradx-runtime/hydradx_runtime.wasm on-runtime-upgrade --checks all live --uri wss://rpc.hydradx.cloud:443
 ```
 or against HydraDX testnet on Rococo using `--uri wss://rococo-hydradx-rpc.hydration.dev:443`
 

runtime/hydradx/src/migrations.rs

@@ -27,11 +27,6 @@ impl OnRuntimeUpgrade for OnRuntimeUpgradeMigration {
 		weight = weight.saturating_add(orml_unknown_tokens::Migration::<Runtime>::on_runtime_upgrade());
 		log::info!("Migrate Unknown Tokens Pallet to v2 end");
 
-		log::info!("Migrate XCM Pallet to v1 start");
-		weight = weight
-			.saturating_add(pallet_xcm::migration::v1::VersionUncheckedMigrateToV1::<Runtime>::on_runtime_upgrade());
-		log::info!("Migrate XCM Pallet to v1 end");
-
 		let evm_id: u64 = 222_222u64;
 		ChainId::<Runtime>::put(evm_id);
 		weight = weight.saturating_add(<Runtime as frame_system::Config>::DbWeight::get().reads_writes(0, 1));