typesBundle carried overrides for 140 chains inherited from upstream;
none of them is a Pezkuwi chain. The live Pezkuwi and Zagros runtimes
(pezkuwichain, asset-hub-pezkuwichain, people-pezkuwichain, zagros and
its asset hub, bridge hub, collectives, coretime and people) match no
entry and need none: they carry metadata v14+.
The spec files, the Cere chain bundle, the custom derives and the 32
npm packages they came from are removed, among them GPL-3.0-only ones
(pontem, moonbeam, subsocial, jamton) that were bundled into this
Apache-2.0 app. The spec/chain/derives mechanism stays, empty, for a
chain that ever needs one. typesBundle.ts is regenerated (15 lines).
yarn.lock loses 3250 lines, elliptic and the old @polkadot/api trees
with them.
@logion/node-api (Apache-2.0) and @digitalnative/type-definitions (MIT)
were imported only for their type definitions, and each brought an old
@polkadot/api tree with it (util-crypto 6/7, elliptic, uuid). The
definitions are now in the spec files, with their source and license.
Checked by serialising each resulting bundle with key order and
undefined preserved: byte-identical to what the packages produced
(logion 27715 bytes, standard and opportunity 1778 each).
RegistryTypes does not model a struct's `_alias` map, which the registry
accepts; the merged latest logion types are cast at that one point.
The resolutions held the whole tree on wasm-crypto 7.5.17, util-crypto
14.0.25, api 16.5.36, ui 3.17.2 and extension-dapp 0.62.20, the
releases where ed25519, secp256k1, derivation and bip39 were not
implemented in wasm-crypto. Every @pezkuwi pin moves to the release
that has them: common 14.0.26, wasm 7.5.20, api 16.5.37, ui 3.17.3 and
extension 0.62.27; @pezkuwi/dev ^0.85.12. After `yarn dedupe` each
@pezkuwi package resolves to a single version.
- Update @pezkuwi/react-identicon to ^3.17.1
- Update @pezkuwi/react-qr to ^3.17.1
- Update @pezkuwi/ui-keyring to ^3.17.1
- Update @pezkuwi/ui-settings to ^3.17.1
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>