@twinsearth/w2m-dsh-plugin 0.6.2 → 0.6.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 +27 -0
- package/package.json +1 -1
- package/src/plugin/tools.mjs +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,33 @@ All notable changes to this project are documented here. The format follows
|
|
|
4
4
|
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project
|
|
5
5
|
adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
6
6
|
|
|
7
|
+
## [0.6.3] — 2026-10-13
|
|
8
|
+
|
|
9
|
+
One fix, and it is the half of v0.6.2 that made the other half usable.
|
|
10
|
+
|
|
11
|
+
### Fixed
|
|
12
|
+
|
|
13
|
+
* **`w2m_status` now reports `encryption.relay_serves_keys`.** v0.6.2 taught the node to tell a relay
|
|
14
|
+
that drops peer keys apart from a peer that has none — and then did not carry the answer to the one
|
|
15
|
+
surface an operator actually reads. The plugin builds its encryption block from an explicit field
|
|
16
|
+
list, and the new field was not on it, so a fleet in exactly the state v0.6.2 exists to explain still
|
|
17
|
+
showed `peers_known: 0` with no way to see why.
|
|
18
|
+
|
|
19
|
+
Measured on the machine that built the release: `w2m_status` returned
|
|
20
|
+
|
|
21
|
+
```json
|
|
22
|
+
"encryption": { "enabled": true, "public_key": "cQshuntt…", "peers_known": 0,
|
|
23
|
+
"handshakes": 0, "encrypted_channels": 0, "plaintext_channels": 0 }
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
while the node underneath it was reporting `relay_serves_keys: false` against the same relay. The
|
|
27
|
+
feature worked and was invisible — which is the failure mode the field was added to remove, one
|
|
28
|
+
layer up.
|
|
29
|
+
|
|
30
|
+
`?? null`, not `?? 0`, because the value is three-valued and collapsing it would accuse the relay
|
|
31
|
+
before it had been tested: `null` means no announcement has proved it either way (or this node has
|
|
32
|
+
no key of its own, so it never asked), `false` means the relay dropped the key we sent.
|
|
33
|
+
|
|
7
34
|
## [0.6.2] — 2026-10-13
|
|
8
35
|
|
|
9
36
|
The release that stops a broken *relay* from being reported as an out-of-date *peer*, and stops a
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@twinsearth/w2m-dsh-plugin",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.3",
|
|
4
4
|
"description": "DSH: Windows2MacOS — drive the same project on online Windows and macOS machines from one DeepSeek account, across networks and regions. P2P hole punching is the default path (relay + shared server as rendezvous, ledger and fallback), with a bundled STUN responder, Tailscale/public-VPS/tunnel shapes, Rabbit relay + per-machine Localside + eight DSH tools (replicate / split), nine aggregate verdicts and signed requests.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "lib/index.js",
|
package/src/plugin/tools.mjs
CHANGED
|
@@ -177,7 +177,7 @@ const MAX_STAGES = 16;
|
|
|
177
177
|
* `package.json` during `scripts/pack.mjs` rather than hand-maintained, and `W2M_PLUGIN_VERSION`
|
|
178
178
|
* overrides it at runtime for tests and packagers.
|
|
179
179
|
*/
|
|
180
|
-
const PLUGIN_VERSION = '0.6.
|
|
180
|
+
const PLUGIN_VERSION = '0.6.3';
|
|
181
181
|
|
|
182
182
|
/** How long any single HTTP call may take before it is aborted, in milliseconds. */
|
|
183
183
|
const DEFAULT_REQUEST_TIMEOUT_MS = 15_000;
|