Commit Graph
12 Commits
Author SHA1 Message Date
Satoshi Qazi Muhammed 00f3f75643 Release 16.5.39
Carries the tx generator fix (struct and enum arguments keep their object
input) on top of 16.5.38. All packages and their exact internal pins move
to 16.5.39.
2026-10-08 23:32:40 +04:00
Satoshi Qazi Muhammed d0c07ebba2 typegen: give getSimilarTypes the registry's name for tx arguments
The tx generator rebranded each argument's lookup name (SpWeightsWeightV2Weight
to PezspWeightsWeightV2Weight) before asking getSimilarTypes for its inputs.
The registry knows the type only by its metadata name, so for every lookup
type the class checks found nothing and the generated signature was the bare
type: multisig.asMulti took `maxWeight: PezspWeightsWeightV2Weight` with no
`{ refTime?: any; proofSize?: any }`, and a timepoint without
`{ height?: any; index?: any }`. Passing a plain object, as every caller
does, was a type error.

getSimilarTypes and formatType now get the metadata name, as the query
generator already does for storage keys, and return rebranded names
themselves; the rebranded name is what goes into the imports and the
used-type list. The augment is regenerated (yarn build:metadata, 1070
passed). Only tx.ts files change; enum variant names are untouched.
2026-10-08 23:25:36 +04:00
Satoshi Qazi Muhammed ca7f3bcc2f Release 16.5.38
Carries the typegen fix for types that contain an account (a0b19f4) and the
api-augment regenerated with it; nothing else changed since 16.5.37
(2a35891). All packages and their exact internal pins move to 16.5.38.
2026-10-08 23:10:31 +04:00
Satoshi Qazi Muhammed a0b19f4916 typegen: keep array and null inputs for types that contain an account
getSimilarTypes widened lookup types by name before its class checks, with
type.includes('AccountId32') and type.includes('MultiAddress'). Those also
match every type that only contains one: Vec<AccountId32>,
Option<AccountId32>, ITuple<[AccountId32, u32]>, Vec<MultiAddress>. They
were widened like a bare account and returned before reaching the Vec,
Option or Tuple branch, so the generated augment typed
multisig.asMulti(otherSignatories) as `Vec<AccountId32> | string |
Uint8Array` (no string[]), an Option<AccountId32> argument without null,
and a tuple key without its tuple form.

The names are now matched whole. The augment is regenerated
(yarn build:metadata); for these types it now matches what upstream
generates, e.g. `Vec<AccountId32> | (AccountId32 | string | Uint8Array)[]`.
2026-10-08 23:02:46 +04:00
Satoshi Qazi Muhammed 611d410f28 Restore source package manifests and release 16.5.37
The packages/*/package.json files were the manifests the build writes
into build/, committed back over the source ones: exports maps of
thousands of entries pointing at ./cjs/* files, main at ./cjs/index.js,
module and types set. pezkuwi-dev-build-ts generates those fields
itself; in the source they pointed at files that only existed because
build output had been committed too. main, module, types, exports,
browser, react-native and sideEffects are back in the source form of
the upstream manifests; every other field is unchanged.

- @pezkuwi/* common dependencies 14.0.25 -> 14.0.26 (wasm-crypto 7.5.20
  underneath, with working ed25519 and secp256k1)
- the root resolutions forcing common 14.0.25 and wasm 7.5.4 onto the
  whole tree are removed; only the typescript pin remains
- @pezkuwi/dev, dev-test and dev-ts ^0.85.12
- the deno script is removed
- version 16.5.37
2026-10-08 03:23:10 +04:00
Satoshi Qazi Muhammed 99d47a034e PortableRegistry: alias both the pezsp_ and the sp_ type paths
The rename replaced the sp_*, frame_* and polkadot_runtime_common paths
in PATHS_ALIAS and in the extrinsic and event-record lookups with their
pezsp_*, pezframe_* and pezkuwi_runtime_common forms. Live Pezkuwi
chains expose the pez* paths, but metadata built from upstream
Substrate (including every metadata fixture in types-support) exposes
the original ones, and for those the registry no longer resolved
Weight, MultiAddress, AccountId32, the unchecked extrinsic or the event
record: 26 tests failed and the api suite hung.

Every alias now matches both forms, and the extrinsic and event-record
lookups fall back from the pez* name to the upstream one. The augment
interfaces are regenerated from the fixtures with the restored aliases
(AccountId32, EthereumAddress, MultiAddress, ... instead of the raw
path names), which is also what the registry hands out at runtime.
2026-10-08 03:23:10 +04:00
Satoshi Qazi Muhammed 6468c53ec8 Drop the Deno target
The mod.ts entry points and import_map.in.json fed a deno.land/x
publication that never existed. pezkuwi-common dropped the same target.
2026-10-08 03:23:10 +04:00
Kurdistan Tech Ministry 1be455e7ad release: v16.5.36 - npm package structure fix
- Published from build/ directories for correct npm structure
- Updated common dependencies to 14.0.25
- Added AuthorizeCall signed extension support
- All packages now have index.js at root level
2026-02-01 21:45:29 +03:00
Kurdistan Tech Ministry d069be2314 fix: update cross-package dependencies to 16.5.18 2026-01-31 17:15:48 +03:00
Kurdistan Tech Ministry 2db0d19928 fix: update pezkuwi mainnet genesis hash and remove npm token from repo
- Update genesis hash to mainnet value
- Remove npmAuthToken from .yarnrc.yml (use GitHub Secrets instead)
- Add pezsp_* and pezframe_* path support in PortableRegistry
2026-01-31 07:33:44 +03:00
Kurdistan Tech Ministry c2f759f58d chore: update to version 16.5.9, align with pezkuwichain brand and fix tests 2026-01-11 11:32:56 +03:00
Kurdistan Tech Ministry d5f038faea Rebrand: polkadot → pezkuwi, substrate → bizinikiwi, kusama → dicle 2026-01-07 02:29:40 +03:00