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)
${{ github.workspace }} template expands to host path at parse time,
but inside Docker containers the actual workspace path is different.
Use $GITHUB_WORKSPACE environment variable which is correct at runtime.
- tests-evm.yml: Use paritytech repositories for external test tools
(revive, revive-differential-tests, evm-test-suite are external
dependencies, not part of Pezkuwi SDK rebrand)
- check-getting-started.yml: Add HOME=/root for container jobs
(fixes rustup HOME directory mismatch error)
- Add PEZKUWI_TEMPLATE_SOURCE env var support to getting-started.sh
for using local templates instead of cloning from external repos
- Update workflow to build templates within SDK workspace context
since templates use workspace inheritance
- Add package names to matrix for correct cargo -p targets
- Add SKIP_WASM_BUILD=1 to avoid serde_core wasm32 issues
pezkuwichain