- Update CRATES_PUBLISH_PLAN.md with Level 0-2 completion status
- Fix binary-merkle-tree and related dependencies
- Add runtime_logger_tests.rs
- Update various Cargo.toml files
Removed pezsp-crypto-hashing-proc-macro from dev-dependencies of pezsp-crypto-hashing.
The proc-macro integration tests are already in the proc-macro crate itself.
The 25_tickets_100_auths.bin file was gitignored by the global *.bin
rule but is required for cargo-check-all-benches CI job. This adds an
exception to .gitignore and includes the benchmark data file.
* 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)
These crates were excluded from umbrella due to `publish = false`.
Since Polkadot SDK publishes them, we should too.
- Remove publish = false from pezpallet-root-testing
- Remove publish = false from pezpallet-xcm-benchmarks
- Regenerate umbrella to include both crates
- Rename CLI argument --pallet to --pezpallet (with --pallet as alias)
- Rename --pallets to --pezpallet, --exclude-pallets to --exclude-pezpallets
- Update benchmark subcommand from 'pallet' to 'pezpallet'
- Rename check-frame-omni-bencher.yml to check-pezframe-omni-bencher.yml
- Update all benchmark scripts to use new argument names
- Update cmd.py to use pezframe-omni-bencher and --pezpallet
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>
pezkuwi-subxt, pezkuwi-subxt-rpcs, and pezkuwi-subxt-lightclient
all require either 'native' or 'web' feature to be enabled. When
umbrella's node feature enables these dependencies with
default-features = false, the default 'native' feature is not
propagated, causing compile_error! in all three crates.
Added "dep?/native" propagation for all three subxt crates in
the node feature.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Update vendor/pezkuwi-zombienet-sdk/rustfmt.toml to stable-only
- Reformat 74 vendor files with stable rustfmt
- Remove nightly-only features causing CI failures
pezkuwichain
SatoshiQaziMuhammed