@mmmbuto/nexuscrew 0.8.48 → 0.8.49
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
CHANGED
|
@@ -4,6 +4,24 @@ All notable changes to NexusCrew are tracked here.
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
## 0.8.49 — 2026-08-04 — "Whose Identity"
|
|
8
|
+
|
|
9
|
+
- Share can be enabled over a reverse channel again. A reverse slot listener
|
|
10
|
+
answers an ownership challenge signed over `(port, generation, instanceId)`,
|
|
11
|
+
and the far end builds that challenge with the id of *this* installation —
|
|
12
|
+
us, as seen from there. The listener announced the id of the **remote** node
|
|
13
|
+
instead, so the two ends signed different tuples and the proof never matched.
|
|
14
|
+
The refusal arrives as a typed `409`, which is final by design, so no amount
|
|
15
|
+
of retrying could help and Share stayed off. Present since 0.8.45. The
|
|
16
|
+
listener now announces its own instance id, and refuses to open at all when
|
|
17
|
+
that id is unknown rather than opening one nobody can validate.
|
|
18
|
+
|
|
19
|
+
- A failed Share now says why. The server had already classified the failure
|
|
20
|
+
and redacted it — `code` and `detail` travelled in the response — but the
|
|
21
|
+
interface showed only the headline, which is the same four words whether the
|
|
22
|
+
peer is unreachable, the credential was refused, the hub answered 5xx or a
|
|
23
|
+
slot proof was refused. Both are now shown.
|
|
24
|
+
|
|
7
25
|
## 0.8.48 — 2026-08-04 — "Federated Terminal, Scroll and Names"
|
|
8
26
|
|
|
9
27
|
- Federated terminals no longer stay black. A WebSocket upgrade arriving on a
|