🎉 Publish Wallets Release

packages/sdk/CHANGELOG.md

@@ -1,5 +1,18 @@
 # @swapkit/sdk
 
+## 5.1.5
+
+### Patch Changes
+
+- [#219](https://github.com/swapkit/wallets/pull/219) [`14dfb3f`](https://github.com/swapkit/wallets/commit/14dfb3f145a33e246c456f6cb2a98c27d10b4540) Thanks [@github-actions](https://github.com/apps/github-actions)! - Update SwapKit SDK dependencies:
+- [#209](https://github.com/swapkit/wallets/pull/209) [`542e1f8`](https://github.com/swapkit/wallets/commit/542e1f8126b4045c9b38e8a4371380223745aa49) Thanks [@hippocampusSK](https://github.com/hippocampusSK)! - The keystore wallet now declares that it can sign Bitcoin messages (`signingSupport[Chain.Bitcoin].btcMessage`, carried on the connected Bitcoin wallet as `signing.btcMessage`), so flows that need one, like cancelling a Harbor Bitcoin limit order, can use it. A keystore using a Bitcoin address type that Bitcoin message signatures cannot express, such as Taproot, does not declare it. (via @swapkit/wallets@6.2.0)
+- [#215](https://github.com/swapkit/wallets/pull/215) [`5904076`](https://github.com/swapkit/wallets/commit/5904076f28afd4866331fd735f3b0d7f6dd2adaf) Thanks [@hippocampusSK](https://github.com/hippocampusSK)! - Ledger keeps signing Zcash through the NU7 network upgrade (mainnet block 3,543,405, around 5 November 2026). The Ledger Zcash signer kit moves to 0.9.0, the first release whose mainnet table carries the NU7 consensus branch id `0x77190ad9`, and the client now maps a transaction built under NU7 to that activation height. Each previous transaction is framed with the same height, so a v4 input is hashed under the branch the transaction is signed for rather than the kit's default. Before NU7 nothing changes: transactions built under Ironwood still sign under Ironwood. The device must run the Zcash app release that accepts the NU7 branch id, installed from Ledger Live. The Device Management Kit moves to 1.11.0, with the Ethereum signer kit and context module on the matching releases, and `@swapkit/utxo-signer` to 3.2.0 across the wallet packages. (via @swapkit/wallets@6.2.0)
+- [#215](https://github.com/swapkit/wallets/pull/215) [`5904076`](https://github.com/swapkit/wallets/commit/5904076f28afd4866331fd735f3b0d7f6dd2adaf) Thanks [@hippocampusSK](https://github.com/hippocampusSK)! - Update SwapKit SDK dependencies: (via @swapkit/wallets@6.2.0)
+- [#182](https://github.com/swapkit/wallets/pull/182) [`190babc`](https://github.com/swapkit/wallets/commit/190babc006c9ff5cc54fc71e3098f1556e7ab2ed) Thanks [@hippocampusSK](https://github.com/hippocampusSK)! - Add HyperCore (Hyperliquid) support to the Trezor wallet for USDC transfers and swaps. (via @swapkit/wallets@6.2.0)
+- [#208](https://github.com/swapkit/wallets/pull/208) [`6e087ca`](https://github.com/swapkit/wallets/commit/6e087ca27f3890c5ea627481b9a2d3cffff14234) Thanks [@mfaizan1](https://github.com/mfaizan1)! - Sign Zcash sends and swaps on Ledger again. The connector told the device that change returns to the account's receive address, and the Zcash app only accepts a change path on the internal chain (`…/1/x`), so every transaction was refused with status `6986` before the review screen. Change on a receive address is now left for the device to show as a regular output, which you approve along with the payment. (via @swapkit/wallets@6.2.0)
+- [#216](https://github.com/swapkit/wallets/pull/216) [`894f4bd`](https://github.com/swapkit/wallets/commit/894f4bd0e6a42deed66e9400abd18fbf625ed574) Thanks [@hippocampusSK](https://github.com/hippocampusSK)! - Trezor signs transparent Zcash as version 5 transactions, carrying the branch id, expiry and lock time of the transaction it was handed instead of a fixed version 4 header. Signing as v4 made Trezor Connect fetch and parse every previous transaction, and it cannot read the v6 transactions in use since Ironwood, so spending ZEC received that way failed with "Transaction has unexpected data"; v5 commits to the input amounts directly and needs no previous transactions. It also keeps Trezor working through the NU7 network upgrade (mainnet block 3,543,405, around 5 November 2026), which rejects version 4 transactions: the SDK resolves the branch id and version from the block height, and the signer now passes them through. `signPCZT` returns a v5 PCZT carrying the header Trezor signed, so the transaction extracted from it matches the signatures. A transaction handed over as raw bytes carries no input amounts, so the signer now looks them up by outpoint before signing and refuses when one cannot be resolved, instead of asking the device to sign zero-value inputs. (via @swapkit/wallets@6.2.0)
+- [#210](https://github.com/swapkit/wallets/pull/210) [`4e3f9f7`](https://github.com/swapkit/wallets/commit/4e3f9f7f4c955f2eca10ca2419d3db5089a8c0e2) Thanks [@hippocampusSK](https://github.com/hippocampusSK)! - OneKey now connects Stellar, TON, TRON and NEAR on mainnet, alongside its EVM chains. Bitcoin and Solana connections work again: they were looking for wallet providers the OneKey extension never exposes, so connecting either chain always failed. A TRON or Stellar signature from OneKey is rejected if it covers a different transaction than the one requested. (via @swapkit/wallets@6.2.0)
+
 ## 5.1.4
 
 ### Patch Changes

packages/sdk/package.json

@@ -45,12 +45,21 @@
       "types": "./dist/types/wallets.d.ts"
     }
   },
-  "files": ["dist/", "src/"],
+  "files": [
+    "dist/",
+    "src/"
+  ],
   "homepage": "https://github.com/swapkit/wallets",
   "license": "SEE LICENSE IN LICENSE",
   "name": "@swapkit/sdk",
-  "publishConfig": { "access": "public" },
-  "repository": { "directory": "packages/sdk", "type": "git", "url": "git+https://github.com/swapkit/wallets.git" },
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "directory": "packages/sdk",
+    "type": "git",
+    "url": "git+https://github.com/swapkit/wallets.git"
+  },
   "scripts": {
     "build": "bun run ./build.ts",
     "build:clean": "rm -rf dist && bun run ./build.ts",
@@ -59,5 +68,5 @@
     "type-check:go": "tsgo"
   },
   "type": "module",
-  "version": "5.1.4"
+  "version": "5.1.5"
 }