Uncomment dev-dependencies that were previously commented out to break
circular dependencies. These dependencies are needed for tests to compile
when running clippy with --all-targets --all-features.
Changes include:
- pezkuwi/node/*: Add pezkuwi-node-subsystem-test-helpers, pezkuwi-primitives-test-helpers
- pezkuwi/xcm/*: Add pezpallet-xcm, xcm-pez-simulator
- pezcumulus/client/*: Add test client, runtime, and sproof builder deps
- bizinikiwi/pezframe/*: Add bizinikiwi-test-utils, pezframe-support-test,
pezpallet-transaction-payment, pezpallet-example-basic, etc.
- vendor/pezkuwi-zombienet-sdk: Fix imports from zombienet_sdk to pezkuwi_zombienet_sdk
All runtime-benchmarks feature flags have been updated accordingly.
cargo clippy --all-targets --all-features --workspace now passes.
The serde feature was enabling primitive-types/serde which transitively
enables std -> fixed-hash/std -> rand/std -> getrandom. This fails on
wasm32-unknown-unknown target. Using only primitive-types/serde_no_std
provides serde support without the std dependency chain.
- Update .gitignore for local Claude files and generated artifacts
- Add MAINNET_ROADMAP.md with deployment phases
- Add zombienet test configuration files
- Add Pezkuwi-specific subxt examples for token transfers
- Fix serde optional dependency issues by adding dep:serde to serde features (24 crates)
- Run zepter to propagate runtime-benchmarks, std, try-runtime, serde, experimental, with-tracing, tuples-96 features
- Regenerate umbrella crate with proper feature propagation
- Format all TOML files with taplo
This resolves check-umbrella and check-zepter CI failures.
- pezstaging-node-cli: use direct workspace deps instead of umbrella
- templates/teyrchain/runtime: xcm->pezstaging-xcm, teyrchain-info->pezstaging-teyrchain-info
- yet-another-teyrchain/runtime: same xcm and teyrchain-info fixes
Change Ed25519 AURA key detection from 'asset-hub-polkadot' to
'asset-hub-pezkuwi' to properly generate Ed25519 keys for
asset-hub-pezkuwichain collators.
This fixes the teyrchain collation issue where AURA keys were
being generated with Sr25519 instead of Ed25519.
Changes:
- chain_spec.rs: Update chain ID check for Ed25519 detection
- keystore.rs: Rename parameter for clarity
- keystore_key_types.rs: Update function parameters and docs
- spawner.rs: Update Ed25519 detection logic
- Remove circular dev-deps from pezframe-support-procedural
- Remove circular dev-deps from pezframe-support
- Remove circular dev-deps from pezframe-system
- Remove circular dev-deps from pezframe-benchmarking
- Comments note that tests moved to integration test crates
- 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)
pezkuwichain
SatoshiQaziMuhammed