The serde_core + Rust 1.88 issue only affects wasm32v1-none target.
wasm32-unknown-unknown works fine, and wasm-builder falls back to it
automatically when wasm32v1-none is not installed.
- Remove all `rustup target add wasm32v1-none` steps (12 files)
- Remove SKIP_WASM_BUILD=1 env vars added as workaround (28 occurrences)
- Re-enable quick-benchmarks job (tests.yml)
- Re-enable check-core-crypto-features job (checks.yml)
- Re-enable 15 build/zombienet jobs (build-publish-images.yml)
- Re-enable test-pezframe-examples-compile-to-wasm and
test-deterministic-wasm jobs (tests-misc.yml)
Tracking: #355, #357, #358
Upstream: https://github.com/serde-rs/serde/issues/3021 (still open)
Workflows updated:
- tests-evm.yml: differential-tests and evm-test-suite jobs
- tests-linux-stable-coverage.yml: test-linux-stable-coverage job
- tests-linux-stable-xp.yml: both test jobs (currently disabled but ready)
- tests-misc.yml: test-full-crypto-feature job
All changes include tracking comment for issue #358.
The serde_core + Rust 1.88 + wasm32 combination causes duplicate lang item
error. These jobs don't require WASM output, so skip it.