* docs: update workflow plan with completed CI fixes
* fix(ci): remove wasm32v1-none target installation to fix serde_core compilation
This removes the explicit `rustup target add wasm32v1-none` step from CI
workflows. When wasm32v1-none is installed, the wasm-builder uses it instead
of wasm32-unknown-unknown, which causes serde_core 1.0.228 to fail compilation
with "relaxing a default bound only does something for ?Sized" errors.
By not installing wasm32v1-none, the wasm-builder automatically falls back to
wasm32-unknown-unknown which compiles successfully.
This aligns with Polkadot SDK's CI configuration which also does not explicitly
install wasm32v1-none.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Fixes getrandom/duplicate lang item errors in WASM builds by ensuring
the wasm32v1-none target is installed before running cargo builds that
involve WASM compilation. This is required for Rust 1.84+ where the
bizinikiwi-wasm-builder uses wasm32v1-none instead of wasm32-unknown-unknown.
Affected workflows:
- tests.yml (quick-benchmarks)
- tests-linux-stable.yml (test-linux-stable-int, test-linux-stable-runtime-benchmarks)
- tests-misc.yml (test-deterministic-wasm)
- build-publish-images.yml (build-linux-stable, build-linux-bizinikiwi)
- check-pezframe-omni-bencher.yml (quick-benchmarks-omni, run-pezframe-omni-bencher)
The package was renamed from pez-staging-node-cli to pezstaging-node-cli
during the rebrand but the workflow files still referenced the old name.
Files updated:
- build-publish-images.yml
- release-20_build-rc.yml
- release-reusable-rc-build.yml
- tests-linux-stable.yml
- tests.yml
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
pezkuwichain