fix: add wasm32v1-none target to CI workflows

Add rustup target add wasm32v1-none step to: - tests-misc.yml: test-pezframe-examples-compile-to-wasm, cargo-check-benches, check-metadata-hash, cargo-check-each-crate - tests-linux-stable.yml: test-linux-stable-int, test-linux-stable-runtime-benchmarks, test-linux-stable, test-linux-stable-no-try-runtime - build-misc.yml: build-runtimes-polkavm This fixes WASM build failures in container jobs where the wasm32v1-none target is not available by default.
2026-01-26 15:42:21 +03:00
parent 7638b9ddf5
commit 5602586e55
3 changed files with 23 additions and 1 deletions
@@ -43,6 +43,9 @@ jobs:
          rustup show
          rustup +nightly show

+      - name: Add wasm32v1-none target
+        run: rustup target add wasm32v1-none || true
+
      - name: Build
        env:
          BIZINIKIWI_RUNTIME_TARGET: riscv