Skip to content

Releases

v2.7.1

Choose a tag to compare

@github-actions github-actions released this 03 Nov 20:57

Security

  • sdk-core no longer allows vulnerable releases of its HTTP stack. It depended on axios ^1.7.0, a range that lets an install with an existing lockfile stay on an axios release with known high-severity advisories, and on follow-redirects only through axios. The floors are now axios ^1.20.0 and follow-redirects ^1.16.2 (a direct dependency, so the floor holds whichever axios is picked).
    • axios before 1.20.0: a ReDoS in the data-URL parser that freezes the event loop, a ReDoS in proxy bypass handling reachable through an untrusted redirect Location, redirect-based SSRF when maxRedirects: 0 is not enforced by the fetch adapter, an HTTP/2 adapter that bypasses configured DNS lookup and proxy controls, and several prototype-pollution gadgets in request configuration.
    • follow-redirects 1.16.0 and 1.16.1: credential headers (Authorization and similar) can follow a cross-origin redirect.
    • What to do: upgrade @activeledger/sdk-core (and sdk-node or sdk-web, which depend on it) to 2.7.1, then refresh your lockfile so it resolves axios 1.20.0 or newer and follow-redirects 1.16.2 or newer (for example npm update axios follow-redirects, or pnpm update axios follow-redirects -r). Installing 2.7.1 alone is not enough if your lockfile already pins the old releases. This repository's own lockfile already resolved patched releases; the change is to the range everyone else installs.
    • No API change.

Tests

  • Tests fail if the declared floors are lowered or this repository's lockfile resolves a release below them.

v2.7.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 10:59

Changed

  • A reply counts as committed only if it is a 2xx JSON object with a $summary object. Connection.sendTransaction now rejects a 2xx whose body is {}, an HTML proxy page or empty, and onboardKey sets an identity only when the reply is committed (a $summary with no errors) and contains the new stream. A ledger rejection delivered as HTTP 200 still resolves from sendTransaction, carrying its $summary.errors. What to do: if you treated any resolved sendTransaction as success, check isCommitted(response) (new export) instead.
  • sdk-node importKey validates the key file. It checks the type, the key encodings and lengths, and that the private and public keys belong together. A file that fails now rejects with a clear error where it used to be accepted. What to do: re-export any key file that was assembled by hand or edited.
  • sdk-web fromHex rejects non-hex characters and odd lengths (an optional 0x is accepted, as in sdk-node). What to do: pass valid hex.

Fixed

  • sdk-web restoreBIP39Key(..., { validate: false }) rejected a non-BIP-39 phrase that sdk-node accepts, because @scure/bip39 validates inside mnemonicToSeedSync. The seed is now computed with PBKDF2-HMAC-SHA512 directly, so the same phrase gives the same key on both. New export unvalidatedSeed in recovery.
  • ISummaryObject had no errors, so TypeScript users had to cast $summary. It now has an optional errors?: string[], and the cast in onboardKey is gone.
  • sdk-node verify threw on a public key OpenSSL cannot load (for example an uncompressed point not on secp256k1). It now returns false, as sdk-web does.

Performance

  • sdk-node secp256k1 signing parses the private key once per signature instead of twice. Measured on Node 24.19 (500 signs per sample, WSL2): 1.12-1.25 ms to 0.78-0.79 ms per signature. Output is unchanged.

Tests and CI

  • Coverage for Connection, LedgerEvents, labelledTransaction options, node key file import and export, ASN.1 and the web wrappers.
  • scripts/smoke-pack.mjs (build, pack and install the three packages into a fresh project) now runs in CI.
  • Live-network suite for sdk-node, skipped unless AL_NODES and AL_STORAGE are set.
  • scripts/verify-input-validation.mjs checks that sdk-node and sdk-web agree on input validation, and runs in npm test.
  • README links to the hosted documentation.

v2.6.0

Choose a tag to compare

@github-actions github-actions released this 27 Sep 22:28
d27832c

Full Changelog: v2.5.1...v2.6.0

v2.5.1

Choose a tag to compare

@github-actions github-actions released this 23 Sep 21:27

What's Changed

  • fix(node): RSA signing broken by low-S folding; refuse ungeneratable key types by @AdmWalker in #19

Full Changelog: v2.5.0...v2.5.1

v2.5.0

Choose a tag to compare

@github-actions github-actions released this 21 Sep 07:22

Full Changelog: v2.4.0...v2.5.0

v2.4.0

Choose a tag to compare

@github-actions github-actions released this 20 Sep 07:30

Full Changelog: v2.3.0...v2.4.0

v2.3.0

Choose a tag to compare

@github-actions github-actions released this 20 Sep 07:26

Full Changelog: v2.2.0...v2.3.0

v2.2.0

Choose a tag to compare

@github-actions github-actions released this 19 Sep 21:26

What's Changed

  • fix: the GitHub release step was skipped whenever release.yml called it by @AdmWalker in #7
  • test: cross-repo interop harness and post-quantum vectors by @AdmWalker in #9
  • Publish secp256k1 test vectors alongside the post-quantum ones by @AdmWalker in #10
  • Publish deterministic secp256k1 signatures and guard low-S coverage by @AdmWalker in #11
  • Publish the high-S form of each secp256k1 signature by @AdmWalker in #12
  • Correct why the high-S form is published by @AdmWalker in #13
  • sdk-node emitted high-S signatures about half the time by @AdmWalker in #14
  • falcon-512 keygen IS portable from a seed — the header said otherwise by @AdmWalker in #15
  • feat: PayloadHandler - sign and verify things that are not transactions by @AdmWalker in #8
  • feat: derive keys from a seed, and recover post-quantum keys from a phrase by @AdmWalker in #16

Full Changelog: v2.1.1...v2.2.0

v2.1.1

Choose a tag to compare

@AdmWalker AdmWalker released this 14 Sep 12:08

What's Changed

  • docs: lead with post-quantum keys, and show how to choose one by @AdmWalker in #5
  • ci: drop lerna, and actually create the GitHub release by @AdmWalker in #6

Full Changelog: v2.1.0...v2.1.1

v2.1.0

Choose a tag to compare

@AdmWalker AdmWalker released this 14 Sep 11:57
775b9e6

What's Changed

Full Changelog: v2.0.2...v2.1.0