fix: replace wasm32-unknown-unknown with wasm32v1-none in crypto checks and scripts

The serde_core + wasm32-unknown-unknown combination causes duplicate
lang item errors (panic_impl). Using wasm32v1-none avoids the fallback
to -Z build-std which triggers the conflict.
This commit is contained in:
2026-02-23 11:15:06 +03:00
parent acb2b3f181
commit 83e29dba8c
6 changed files with 15 additions and 7 deletions
@@ -4,7 +4,7 @@ export RUSTFLAGS="-Cdebug-assertions=y -Dwarnings"
cargo check --release
export RUSTFLAGS="$RUSTFLAGS --cfg bizinikiwi_runtime"
T=wasm32-unknown-unknown
T=wasm32v1-none
cargo check --release --target=$T --no-default-features
cargo check --release --target=$T --no-default-features --features="full_crypto"
cargo check --release --target=$T --no-default-features --features="serde"
@@ -1,7 +1,7 @@
#!/usr/bin/env -S bash -eux
export RUSTFLAGS="-Cdebug-assertions=y -Dwarnings --cfg bizinikiwi_runtime"
T=wasm32-unknown-unknown
T=wasm32v1-none
cargo check --target=$T --release --no-default-features --features="bls-experimental"
cargo check --target=$T --release --no-default-features --features="full_crypto,bls-experimental"
@@ -5,5 +5,5 @@ cargo check --release
cargo check --release --features="bandersnatch-experimental"
export RUSTFLAGS="$RUSTFLAGS --cfg bizinikiwi_runtime"
T=wasm32-unknown-unknown
T=wasm32v1-none
cargo check --release --target=$T --no-default-features