Fix build-release-binaries workflow by switching from musl to glibc target

.github/workflows/build-release-binaries.yaml

@@ -16,7 +16,7 @@ jobs:
     strategy:
       matrix:
         platform:
-          - { os: ubuntu-22.04, target: x86_64-unknown-linux-musl }
+          - { os: ubuntu-22.04, target: x86_64-unknown-linux-gnu }
           - { os: macos-latest, target: aarch64-apple-darwin }
 
     runs-on: ${{ matrix.platform.os }}
@@ -42,16 +42,11 @@ jobs:
         if: matrix.platform.os == 'macos-latest'
         run: rustup target add aarch64-apple-darwin
 
-      - name: Add musl target
-        if: matrix.platform.os == 'ubuntu-22.04'
-        run: rustup target add x86_64-unknown-linux-musl
-
-      - name: Install deps for musl build
+      - name: Install deps for Linux build
         if: matrix.platform.os == 'ubuntu-22.04'
         run: |
           sudo apt-get update
-          sudo apt-get install -y musl-tools clang build-essential curl llvm-dev libclang-dev linux-headers-generic libsnappy-dev liblz4-dev libzstd-dev libgflags-dev zlib1g-dev libbz2-dev
-          sudo ln -s /usr/bin/g++ /usr/bin/musl-g++
+          sudo apt-get install -y build-essential libclang-dev
 
       - name: Install deps for macOS build
         if: matrix.platform.os == 'macos-latest'

README.md

@@ -135,8 +135,8 @@ after the migration. [`OnRuntimeUpgrade::pre_upgrade`] returns a [`Vec<u8>`] tha
 arbitrary encoded data (usually some pre-upgrade state) which will be passed to
 [`OnRuntimeUpgrade::pre_upgrade`] after upgrading and used for post checking.
 
-**Note on Multi-Block Migrations (MBM):** If the runtime uses MBMs, the standard 
-`pre_upgrade` and `post_upgrade` checks might be skipped by the executive. To 
+**Note on Multi-Block Migrations (MBM):** If the runtime uses MBMs, the standard
+`pre_upgrade` and `post_upgrade` checks might be skipped by the executive. To
 force these hooks to run synchronously for testing, use the `--disable-mbm-checks` flag.
 
 ### [`VersionedMigration`]
@@ -285,7 +285,7 @@ try-runtime \
 [`Action::OffchainWorker`]: try_runtime_core::commands::Action::OffchainWorker
 [`Action::CreateSnapshot`]: try_runtime_core::commands::Action::CreateSnapshot
 [`Action::FastForward`]: try_runtime_core::commands::Action::FastForward
-[`SharedParams`]: try_runtime_core::shared_parameters::SharedParams
+[`SharedParams`]: try_runtime_core::common::shared_parameters::SharedParams
 [`SharedParams::runtime`]: try_runtime_core::common::shared_parameters::SharedParams::runtime
 [`SharedParams::overwrite_state_version`]: try_runtime_core::common::shared_parameters::SharedParams::overwrite_state_version
 

cli/main.rs

@@ -151,6 +151,10 @@
 //! arbitrary encoded data (usually some pre-upgrade state) which will be passed to
 //! [`OnRuntimeUpgrade::pre_upgrade`] after upgrading and used for post checking.
 //!
+//! **Note on Multi-Block Migrations (MBM):** If the runtime uses MBMs, the standard
+//! `pre_upgrade` and `post_upgrade` checks might be skipped by the executive. To
+//! force these hooks to run synchronously for testing, use the `--disable-mbm-checks` flag.
+//!
 //! ### [`VersionedMigration`]
 //!
 //! It is strongly suggested to use [`VersionedMigration`] when writing custom migrations for
@@ -198,6 +202,8 @@
 //! try-runtime \
 //!     --runtime /path-to-substrate/target/release/wbuild/my-runtime.wasm \
 //!     on-runtime-upgrade \
+//!     # Passing this flag will skip multi-block-migration checks and only run pre_upgrade/post_upgrade checks.
+//!     --disable-mbm-checks \
 //!     live --uri ws://localhost:9999
 //! ```
 //!