Process completed with exit code 127.

Process completed with exit code 127.

failed to run custom build command for `contracts-parachain-runtime v0.39.0`

The process '/home/runner/.cargo/bin/cargo' failed with exit code 101

failed to run custom build command for `contracts-parachain-runtime v0.39.0`

The process '/home/runner/.cargo/bin/cargo' failed with exit code 101

Process completed with exit code 127.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

package `ahash v0.7.6` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

package `elliptic-curve v0.13.5` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

package `bytemuck v1.14.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

[email protected]: Could not find `Cargo.lock` for `/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/contracts-parachain-runtime-0.39.0/Cargo.toml`, while searching from `/tmp/cargo-installB4bt7D/release/build/contracts-parachain-runtime-61b3d5e8d6a644cd/out`. To fix this, point the `WASM_BUILD_WORKSPACE_HINT` env variable to the directory of the workspace being compiled.

build failed, waiting for other jobs to finish...

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

package `bytemuck v1.14.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

[email protected]: Could not find `Cargo.lock` for `/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/contracts-parachain-runtime-0.39.0/Cargo.toml`, while searching from `/tmp/cargo-installMvvnKd/release/build/contracts-parachain-runtime-61b3d5e8d6a644cd/out`. To fix this, point the `WASM_BUILD_WORKSPACE_HINT` env variable to the directory of the workspace being compiled.