ciphermesh 2.7.1 → 2.7.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.
- package/CHANGELOG.md +19 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,25 @@
|
|
|
3
3
|
Notable changes per release. Older versions are reconstructed from the git
|
|
4
4
|
history — the commit bodies and pull requests remain the fuller record.
|
|
5
5
|
|
|
6
|
+
## 2.7.2
|
|
7
|
+
|
|
8
|
+
### Fixed
|
|
9
|
+
|
|
10
|
+
- **The standalone binaries now run on machines other than the one that built
|
|
11
|
+
them.** `sodium-native` resolves its prebuilt addon at runtime, which bun
|
|
12
|
+
cannot follow, so the addon was never embedded — the binary kept an absolute
|
|
13
|
+
path back to the build checkout and died with `Cannot find addon` anywhere
|
|
14
|
+
else. Every binary published before this, including the relay binaries dating
|
|
15
|
+
back to 2.3.0, was affected (#427).
|
|
16
|
+
|
|
17
|
+
The verification was the deeper problem: it ran the binary _on the runner that
|
|
18
|
+
built it_, where the addon resolved through `node_modules`, so every check
|
|
19
|
+
passed while every download was broken. CI now hides the build tree before
|
|
20
|
+
running anything, and the cross-compiled binary is executed under Rosetta
|
|
21
|
+
rather than merely asserting its architecture.
|
|
22
|
+
|
|
23
|
+
**If you downloaded a binary from an earlier release, replace it.**
|
|
24
|
+
|
|
6
25
|
## 2.7.1
|
|
7
26
|
|
|
8
27
|
### Fixed
|
package/package.json
CHANGED