@ledgerhq/hw-app-btc 10.0.5-notarizer.0 → 10.0.6-next.0

package/.turbo/turbo-build.log

@@ -1,4 +1,4 @@
 
-> @ledgerhq/hw-app-btc@10.0.4 build /home/runner/work/ledger-live/ledger-live/libs/ledgerjs/packages/hw-app-btc
+> @ledgerhq/hw-app-btc@10.0.5 build /home/runner/work/ledger-live/ledger-live/libs/ledgerjs/packages/hw-app-btc
 > tsc && tsc -m ES6 --outDir lib-es
 

package/CHANGELOG.md

@@ -1,11 +1,25 @@
 # @ledgerhq/hw-app-btc
 
-## 10.0.5-notarizer.0
+## 10.0.6-next.0
 
 ### Patch Changes
 
 - Updated dependencies []:
-  - @ledgerhq/hw-transport@6.28.5-notarizer.0
+  - @ledgerhq/hw-transport@6.28.6-next.0
+
+## 10.0.5
+
+### Patch Changes
+
+- Updated dependencies []:
+  - @ledgerhq/hw-transport@6.28.5
+
+## 10.0.5-next.0
+
+### Patch Changes
+
+- Updated dependencies []:
+  - @ledgerhq/hw-transport@6.28.5-next.0
 
 ## 10.0.4
 

package/README.md

@@ -297,7 +297,7 @@ This class implements the same interface as BtcOld (formerly
 named Btc), but interacts with Bitcoin hardware app version 2+
 which uses a totally new APDU protocol. This new
 protocol is documented at
-https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md
+<https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md>
 
 Since the interface must remain compatible with BtcOld, the methods
 of this class are quite clunky, because it needs to adapt legacy
@@ -313,7 +313,7 @@ a much cleaner implementation.
 
 This is a new method that allow users to get an xpub at a standard path.
 Standard paths are described at
-https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md#description
+<https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md#description>
 
 This boils down to paths (N=0 for Bitcoin, N=1 for Testnet):
 M/44'/N'/x'/\*\*
@@ -570,7 +570,7 @@ and calls an abstract method to do the actual work.
 Calculates a taproot output key from an internal key. This output key will be
 used as witness program in a taproot output. The internal key is tweaked
 according to recommendation in BIP341:
-https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki#cite_ref-22-0
+<https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki#cite_ref-22-0>
 
 #### Parameters
 
@@ -581,7 +581,7 @@ Returns **[Buffer](https://nodejs.org/api/buffer.html)** The output key
 ### AppClient
 
 This class encapsulates the APDU protocol documented at
-https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md
+<https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md>
 
 #### Parameters
 
@@ -619,7 +619,7 @@ The reason for this is the limited amount of memory available to the app,
 so it can't always store the full psbt in memory.
 
 The signing process is documented at
-https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md#sign_psbt
+<https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md#sign_psbt>
 
 #### Parameters
 
@@ -629,7 +629,7 @@ https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/bitcoin.md#sign_psbt
 
 This class implements the merkle tree used by Ledger Bitcoin app v2+,
 which is documented at
-https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/merkle.md
+<https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/merkle.md>
 
 #### Parameters
 
@@ -639,7 +639,7 @@ https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/merkle.md
 ### MerkleMap
 
 This implements "Merkelized Maps", documented at
-https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/merkle.md#merkleized-maps
+<https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/merkle.md#merkleized-maps>
 
 A merkelized map consist of two merkle trees, one for the keys of
 a map and one for the values of the same map, thus the two merkle
@@ -659,7 +659,7 @@ how to construct output scripts from keys. A "Wallet Policy" consists
 of a "Descriptor Template" and a list of "keys". A key is basically
 a serialized BIP32 extended public key with some added derivation path
 information. This is documented at
-https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/wallet.md
+<https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/wallet.md>
 
 #### Parameters
 
@@ -669,9 +669,9 @@ https://github.com/LedgerHQ/app-bitcoin-new/blob/master/doc/wallet.md
 ### extract
 
 This implements the "Transaction Extractor" role of BIP370 (PSBTv2
-https://github.com/bitcoin/bips/blob/master/bip-0370.mediawiki#transaction-extractor). However
+<https://github.com/bitcoin/bips/blob/master/bip-0370.mediawiki#transaction-extractor>). However
 the role is partially documented in BIP174 (PSBTv0
-https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki#transaction-extractor).
+<https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki#transaction-extractor>).
 
 #### Parameters
 
@@ -682,9 +682,9 @@ Returns **[Buffer](https://nodejs.org/api/buffer.html)**
 ### finalize
 
 This roughly implements the "input finalizer" role of BIP370 (PSBTv2
-https://github.com/bitcoin/bips/blob/master/bip-0370.mediawiki). However
+<https://github.com/bitcoin/bips/blob/master/bip-0370.mediawiki>). However
 the role is documented in BIP174 (PSBTv0
-https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki).
+<https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki>).
 
 Verify that all inputs have a signature, and set inputFinalScriptwitness
 and/or inputFinalScriptSig depending on the type of the spent outputs. Clean
@@ -715,7 +715,7 @@ without actually knowing why. I think we should remove them too.
 
 Writes a script push operation to buf, which looks different
 depending on the size of the data. See
-https://en.bitcoin.it/wiki/Script#Constants
+<https://en.bitcoin.it/wiki/Script#Constants>
 
 #### Parameters
 
@@ -725,8 +725,8 @@ https://en.bitcoin.it/wiki/Script#Constants
 ### PsbtV2
 
 Implements Partially Signed Bitcoin Transaction version 2, BIP370, as
-documented at https://github.com/bitcoin/bips/blob/master/bip-0370.mediawiki
-and https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki
+documented at <https://github.com/bitcoin/bips/blob/master/bip-0370.mediawiki>
+and <https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki>
 
 A psbt is a data structure that can carry all relevant information about a
 transaction through all stages of the signing process. From constructing an

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ledgerhq/hw-app-btc",
-  "version": "10.0.5-notarizer.0",
+  "version": "10.0.6-next.0",
   "description": "Ledger Hardware Wallet Bitcoin Application API",
   "keywords": [
     "Ledger",
@@ -70,21 +70,21 @@
     "sha.js": "2",
     "tiny-secp256k1": "1.1.6",
     "varuint-bitcoin": "1.1.2",
-    "@ledgerhq/hw-transport": "^6.28.5-notarizer.0",
+    "@ledgerhq/hw-transport": "^6.28.6-next.0",
     "@ledgerhq/logs": "^6.10.1"
   },
   "devDependencies": {
     "@types/jest": "^29.5.0",
     "@types/node": "^18.15.3",
     "axios": "^0.25.0",
-    "documentation": "13.2.4",
+    "documentation": "13.2.5",
     "jest": "^28.1.1",
     "rimraf": "^4.4.1",
     "source-map-support": "^0.5.21",
     "ts-jest": "^28.0.5",
     "ts-node": "^10.4.0",
-    "@ledgerhq/hw-transport-mocker": "^6.27.16-notarizer.0",
-    "@ledgerhq/hw-transport-node-speculos": "^6.27.16-notarizer.0"
+    "@ledgerhq/hw-transport-mocker": "^6.27.17-next.0",
+    "@ledgerhq/hw-transport-node-speculos": "^6.27.17-next.0"
   },
   "gitHead": "dd0dea64b58e5a9125c8a422dcffd29e5ef6abec",
   "scripts": {