@integraledger/lcp-binding-evm-x402 0.18.0 → 0.18.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CHANGELOG.md +47 -0
  2. package/package.json +6 -6
package/CHANGELOG.md CHANGED
@@ -1,5 +1,52 @@
1
1
  # @integraledger/lcp-binding-evm-x402
2
2
 
3
+ ## 0.18.2
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies
8
+ - @integraledger/lcp-binding-evm-common@0.18.2
9
+ - @integraledger/lcp-binding-core@0.18.2
10
+ - @integraledger/lcp-kernel@0.18.2
11
+
12
+ ## 0.18.1
13
+
14
+ ### Patch Changes
15
+
16
+ - The line converges on one `zod`, one `viem`, one `@mysten/sui` and one `@stellar/stellar-sdk`
17
+
18
+ The catalogue moved in `75ec0f4` and nothing was released from it, which left the published line
19
+ declaring one set of versions and this repository's source declaring another. Seven packages carry those
20
+ four names in their **published** manifests, so the bump is a change to what consumers must resolve —
21
+ not an internal one:
22
+
23
+ ```
24
+ @stellar/stellar-sdk 17.0.0 -> 17.0.1 lcp-binding-stellar
25
+ @mysten/sui 2.26.2 -> 2.29.0 lcp-binding-sui
26
+ zod 4.4.3 -> 4.5.4 lcp-discovery
27
+ viem 2.55.19 -> 2.56.3 lcp-binding-evm-{common,escrow,mpp,x402}
28
+ ```
29
+
30
+ ⭐ **A PATCH, and the choice is load-bearing rather than cosmetic.** Consumers declare these packages as
31
+ `^0.18.0` peers, and a caret on a `0.x` range is MINOR-LOCKED: `^0.18.0` accepts `0.18.1` and refuses
32
+ `0.19.0`. A minor would therefore force every consumer to edit its peer floor before it could resolve at
33
+ all — turning a dependency convergence into a breaking-change sweep across two repositories. Nothing in
34
+ the public surface changed; only the versions these packages ask their host to supply.
35
+
36
+ ⛔ **WHY IT HAD TO BE RELEASED RATHER THAN LEFT.** A private downstream consumer runs a shared-pin gate,
37
+ which compares its catalogue against what the **published** `@integraledger/*` tarballs declare, read out
38
+ of `node_modules`. With the catalogue moved here and nothing published, that gate reported the line at two
39
+ versions of each name and its `protocol-integration` job went red **with no commit landing in that
40
+ repository to explain it**. Two copies of `zod` in one tree is not a bookkeeping complaint: schemas built
41
+ by one copy fail `instanceof` against the other, and no type-checker sees it.
42
+
43
+ Measured before cutting this: with the catalogue converged, that repository's whole gate passes against
44
+ this line — every stage, 2013 + 731 tests. The divergence was the only finding.
45
+ - Updated dependencies
46
+ - @integraledger/lcp-binding-evm-common@0.18.1
47
+ - @integraledger/lcp-binding-core@0.18.1
48
+ - @integraledger/lcp-kernel@0.18.1
49
+
3
50
  ## 0.18.0
4
51
 
5
52
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@integraledger/lcp-binding-evm-x402",
3
- "version": "0.18.0",
3
+ "version": "0.18.2",
4
4
  "description": "Welds an ATR hash into an x402 instant settlement on any EVM chain.",
5
5
  "keywords": [
6
6
  "lcp",
@@ -44,14 +44,14 @@
44
44
  },
45
45
  "homepage": "https://github.com/IntegraLedger/integra-protocol/tree/main/packages/binding-evm-x402#readme",
46
46
  "dependencies": {
47
- "@integraledger/lcp-binding-core": "0.18.0",
48
- "@integraledger/lcp-binding-evm-common": "0.18.0",
49
- "@integraledger/lcp-kernel": "0.18.0",
50
- "viem": "2.55.19"
47
+ "@integraledger/lcp-binding-core": "0.18.2",
48
+ "@integraledger/lcp-binding-evm-common": "0.18.2",
49
+ "@integraledger/lcp-kernel": "0.18.2",
50
+ "viem": "2.56.3"
51
51
  },
52
52
  "devDependencies": {
53
53
  "@types/node": "24.13.3",
54
- "vitest": "4.1.11"
54
+ "vitest": "5.0.0"
55
55
  },
56
56
  "license": "Apache-2.0",
57
57
  "engines": {