Releases: polkadot-js/common
Releases · polkadot-js/common
v5.6.1
Contributed:
- Fix installation instructions in
@polkadot/x-global
(Thanks to https://github.com/raoulmillais)
Changes:
- Conform to new ss58 encoding with ids up to 16,383 (>= 64 as 2 bytes)
- Use JS sqrt inside
bnSqrt
when value <= MAX_SAFE_INTEGER - Adjust all
Buffer.from
usages, preferUint8Array
where possible - Expand tests for keyring with
vrf{Sign, Verify}
- Align
@polkadot/networks
with latest ss58 registry
v5.5.2
v5.5.1
Changes:
- Added
hdLedger
to util-crypto for Ledger-compatible bip32+ed25519 derivation - Added
hmac{Sha256, 512}
to util-crypto - Add
slip44
indices for Ledger into@polkadot/networks
- Remove
module
entry inpackage.json
(only rely on exports map) - Remove direct references to
global
object, use@polkadot/x-global
- Update
@ledgerhq
dependencies to latest
v5.4.1
Contributed:
- Adjust Ledger app lookup for Polymesh (Thanks to https://github.com/adamdossa)
Changes:
- Allow decimals as
number[]
& symbol asstring[]
in balanceFormat defaults - Add
schnorrkelVrf{Sign, Verify}
to@polkadot/util-crypto
- Export
vrf{Sign, Verify}
on keyring interface - Move
@polkadot/x-rxjs
packages from the api repo - Align
@polkadot/networks
with Substrate master - Explicit edcsa tests for derivation
@polkadot/wasm-crypto
3.2.1
v5.3.1
Important For users of the @polkadot/ledger
package, it is now included in this repo (since it is a general utility) and renamed to @polkadot/hw-ledger
Contributed:
- Add Dock Ledger integration (Thanks to https://github.com/lovesh)
- Add Polymesh Ledger integration (Thanks to https://github.com/adamdossa)
- Add flag for Ledger capabilities on networks (Thanks to https://github.com/Tbaut)
Changes:
- Move
@polkadot/ledger
packages into common - Update
@polkadot/networks
to align with latest Substrate ss58-registry
v5.2.1
v5.1.1
v5.0.1
Important While this package contains no external interface changes, it does now compile and ship both cjs and esm modules. This means that modern bundlers will have more information for tree-shaking available. Additionally when using Node with .mjs
extensions, the esm version imports will be used on recent Node versions. Adding an export map, as here, may have some impacts so a major semver bump is advised. There may be (small) dragons hiding in the dark corners...
Changes:
- Build and expose both cjs and esm via exports map
- Use
import type { ... }
form for all type imports - Align with Substrate master network list
- Debug logs now don't depend on
NODE_ENV
, but ratherDEBUG=<type,type,...>
(*
logs all) - Limit debug console output via
DEBUG_MAX=<number>
value, trimming when passed - Add
memoize
util, allowing for function memoization (as used in the API)
v4.2.1
v4.1.1
Contributed:
- Expand ETH tests, allow for verification against address (Thanks to https://github.com/joelamouche)
Changes:
- Replace pbkdf2 imports with explicit use from sync-only package
- Adjust secp256k1 imports with shared elliptic
- Expand crypto tests for explicit wasm vs JS compares in all cases