@integraledger/lcp-binding-evm-common 0.18.0 → 0.18.1

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