@integraledger/lcp-binding-evm-common 0.18.1 → 0.18.3
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.
- package/CHANGELOG.md +44 -1
- package/package.json +6 -6
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,48 @@
|
|
|
1
1
|
# @integraledger/lcp-binding-evm-common
|
|
2
2
|
|
|
3
|
+
## 0.18.3
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- @integraledger/lcp-authority@0.18.3
|
|
8
|
+
- @integraledger/lcp-binding-core@0.18.3
|
|
9
|
+
- @integraledger/lcp-kernel@0.18.3
|
|
10
|
+
|
|
11
|
+
## 0.18.2
|
|
12
|
+
|
|
13
|
+
### Patch Changes
|
|
14
|
+
|
|
15
|
+
- Eight published CHANGELOGs name a private repository; this supersedes them
|
|
16
|
+
|
|
17
|
+
`0.18.1` is on the registry carrying the name of a private repository in eight packages' `CHANGELOG.md`.
|
|
18
|
+
Measured against the published tarballs rather than the tree — one occurrence each in
|
|
19
|
+
`binding-evm-common`, `binding-evm-escrow`, `binding-evm-mpp`, `binding-evm-x402`, `binding-stellar`,
|
|
20
|
+
`binding-sui`, `discovery` and `evidence`, against a control of **0** in `lcp-kernel`, which is not among
|
|
21
|
+
the eight. The query discriminates; the eight is a measurement.
|
|
22
|
+
|
|
23
|
+
`CHANGELOG.md` is in every one of those packages' `files`, so npm packs it. A consumer holding the
|
|
24
|
+
tarball meets a repository they cannot open — a reference that cannot be followed, and a disclosure that
|
|
25
|
+
the repository exists.
|
|
26
|
+
|
|
27
|
+
⛔ **A published version cannot be recalled, only superseded.** The text is corrected in the tree, but
|
|
28
|
+
`0.18.1` keeps what it shipped: anyone pinning that version still gets it. This bump is the only thing
|
|
29
|
+
that puts a clean CHANGELOG where `latest` resolves.
|
|
30
|
+
|
|
31
|
+
⭐ **No gate could have caught this, and the reason is worth stating.** `check:published-parity` compares
|
|
32
|
+
only files under a declared SOURCE directory — `CHANGELOG.md` is outside its subject set by design, since
|
|
33
|
+
comparing build output and generated prose would make it noisy rather than sharper. So parity reports
|
|
34
|
+
`31 of 31, byte for byte` and is *correct* while the disclosure sits in the artifact. `no-private-referents`
|
|
35
|
+
now sweeps CHANGELOGs in the tree, which stops the next one; neither gate reads a published tarball.
|
|
36
|
+
|
|
37
|
+
⇒ The class that remains open: **a disclosure that exists only in a published artifact is measured by
|
|
38
|
+
nothing here.** The tree is clean, parity is green, and the registry is not.
|
|
39
|
+
|
|
40
|
+
Patch, and the whole `@integraledger/lcp-*` line moves with it — that is what the `fixed` group is for.
|
|
41
|
+
Nothing in any package's behaviour, exports or types changes.
|
|
42
|
+
- @integraledger/lcp-authority@0.18.2
|
|
43
|
+
- @integraledger/lcp-binding-core@0.18.2
|
|
44
|
+
- @integraledger/lcp-kernel@0.18.2
|
|
45
|
+
|
|
3
46
|
## 0.18.1
|
|
4
47
|
|
|
5
48
|
### Patch Changes
|
|
@@ -24,7 +67,7 @@
|
|
|
24
67
|
all — turning a dependency convergence into a breaking-change sweep across two repositories. Nothing in
|
|
25
68
|
the public surface changed; only the versions these packages ask their host to supply.
|
|
26
69
|
|
|
27
|
-
⛔ **WHY IT HAD TO BE RELEASED RATHER THAN LEFT.**
|
|
70
|
+
⛔ **WHY IT HAD TO BE RELEASED RATHER THAN LEFT.** A private downstream consumer runs a shared-pin gate,
|
|
28
71
|
which compares its catalogue against what the **published** `@integraledger/*` tarballs declare, read out
|
|
29
72
|
of `node_modules`. With the catalogue moved here and nothing published, that gate reported the line at two
|
|
30
73
|
versions of each name and its `protocol-integration` job went red **with no commit landing in that
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@integraledger/lcp-binding-evm-common",
|
|
3
|
-
"version": "0.18.
|
|
3
|
+
"version": "0.18.3",
|
|
4
4
|
"description": "Shared EVM machinery for LCP rail bindings: typed-data construction and signature verification.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"lcp",
|
|
@@ -43,15 +43,15 @@
|
|
|
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.
|
|
47
|
-
"@integraledger/lcp-binding-core": "0.18.
|
|
48
|
-
"@integraledger/lcp-kernel": "0.18.
|
|
46
|
+
"@integraledger/lcp-authority": "0.18.3",
|
|
47
|
+
"@integraledger/lcp-binding-core": "0.18.3",
|
|
48
|
+
"@integraledger/lcp-kernel": "0.18.3",
|
|
49
49
|
"viem": "2.56.3"
|
|
50
50
|
},
|
|
51
51
|
"devDependencies": {
|
|
52
|
-
"@types/node": "24.13.
|
|
52
|
+
"@types/node": "24.13.4",
|
|
53
53
|
"fast-check": "4.9.0",
|
|
54
|
-
"vitest": "
|
|
54
|
+
"vitest": "5.0.0"
|
|
55
55
|
},
|
|
56
56
|
"license": "Apache-2.0",
|
|
57
57
|
"engines": {
|