🔨 Update Lisk Core v4 install command to install v4.0.1 or later

LiskArchive · Dec 2, 2023 · b0ad07c · b0ad07c
1 parent f28f696
commit b0ad07c
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -108,9 +108,9 @@ Lisk Migrator has an extensive set of unit tests. To run the tests, please insta
 $ npm test
 ```
 
-## Migrating from Lisk Core v3.1.0 to v4.0.0
+## Migrating from Lisk Core v3.1.0 to v4.0.1
 
-The [migration guide](./docs/migration.md) explains the transition process from Lisk Core v3.1.0 (or later) to Lisk Core v4.0.0 using Lisk Migrator v2.
+The [migration guide](./docs/migration.md) explains the transition process from Lisk Core v3.1.0 (or later) to Lisk Core v4.0.1 using Lisk Migrator v2.
 
 ## Get Involved
 

diff --git a/docs/migration.md b/docs/migration.md
@@ -1,8 +1,8 @@
 # Migration Guide
 
-This section explains how to migrate a Lisk Core v3.1.0 node to Lisk Core v4.0.0 using the Lisk Migrator.
+This section explains how to migrate a Lisk Core v3.1.0 node to Lisk Core v4.0.1 using the Lisk Migrator.
 
-The Lisk Migrator CLI tool will generate a new genesis (snapshot) block for Lisk Core v4.0.0.
+The Lisk Migrator CLI tool will generate a new genesis (snapshot) block for Lisk Core v4.0.1.
 The new genesis block is created based on a snapshot of the existing blockchain (running on Lisk Core v3.1.0) at a pre-determined height.
 
 Lisk Migrator automatically exports the node's Forging Status information to the file named `forgingStatus.json` under the output directory.

diff --git a/src/utils/node.ts b/src/utils/node.ts
@@ -36,7 +36,7 @@ import {
 } from '../constants';
 import { MigratorException } from './exception';
 
-const INSTALL_LISK_CORE_COMMAND = 'npm i -g lisk-core@^4.0.0-rc.1';
+const INSTALL_LISK_CORE_COMMAND = 'npm i -g lisk-core@^4.0.1';
 const INSTALL_PM2_COMMAND = 'npm i -g pm2';
 const PM2_FILE_NAME = 'pm2.migrator.config.json';