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 f5637ff979
commit 541e4b28a3
6 changed files with 15 additions and 7 deletions
+4
View File
@@ -93,6 +93,10 @@ jobs:
image: ${{ needs.preflight.outputs.IMAGE }}
steps:
- uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v4.1.7
- name: Install wasm32v1-none target
run: rustup target add wasm32v1-none
- name: script
id: required
run: |
@@ -180,7 +180,7 @@ jobs:
with:
cache: false
toolchain: ${{ env.RUST_VERSION }}
target: wasm32-unknown-unknown
target: wasm32v1-none
components: cargo, clippy, rust-docs, rust-src, rustfmt, rustc, rust-std
- name: cargo info
+7 -3
View File
@@ -61,12 +61,16 @@ jobs:
steps:
- name: Checkout
uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
- name: Install wasm32v1-none target
run: rustup target add wasm32v1-none
- name: script
run: |
cd bizinikiwi/pezframe/examples/offchain-worker/
RUSTFLAGS="--cfg bizinikiwi_runtime" cargo build --locked --target=wasm32-unknown-unknown --no-default-features
RUSTFLAGS="--cfg bizinikiwi_runtime" cargo build --locked --target=wasm32v1-none --no-default-features
cd ../basic
RUSTFLAGS="--cfg bizinikiwi_runtime" cargo build --locked --target=wasm32-unknown-unknown --no-default-features
RUSTFLAGS="--cfg bizinikiwi_runtime" cargo build --locked --target=wasm32v1-none --no-default-features
test-pezframe-ui:
timeout-minutes: 45
@@ -414,7 +418,7 @@ jobs:
run: |
curl https://sh.rustup.rs -sSf | sh -s -- -y --default-toolchain $RUST_VERSION
source $HOME/.cargo/env
rustup target add wasm32-unknown-unknown
rustup target add wasm32v1-none
rustup component add clippy rust-docs rust-src rustfmt rustc rust-std
- name: Install protobuf
run: brew install protobuf